Performance
(UXPROD-746)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q1 2019 | Parent: | Performance |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | Jakub Skoczen |
| Resolution: | Done | Votes: | 0 |
| Labels: | NFR, suppress-from-capplan | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Performance |
| Back End Estimate: | XXL < 30 days |
| Estimation Notes and Assumptions: | Estimating as XXL |
| Development Team: | Core: Platform |
| Rank: BNCF (MVP Feb 2020): | R1 |
| Rank: Chicago (MVP Sum 2020): | R1 |
| Rank: TAMU (MVP Jan 2021): | R1 |
| Description |
|
Epic to group all backend performance tuning activities. Both database-level and code (business logic) optimization (the latter may be split to another epic). NEEDS: 1 Expected performance baselines for a typical FOLIO deployment. |
| Comments |
| Comment by Kristin Martin [ 30/Jan/19 ] |
|
This seems like a NFR, so Chicago isn't ranking. Let me know if we are mistaken. |
| Comment by Anya [ 06/Feb/19 ] |
|
Cate Boerema is this an NFR? |
| Comment by Jakub Skoczen [ 27/Jun/19 ] |
|
Closing this Epic. Future items of this kind will be grouped in a wide "Platform and DevOps" epic. |