[MGNLPER-60] Investigate performance of periscope and potential mitigations Created: 01/Nov/18 Updated: 22/Nov/18 Resolved: 22/Nov/18 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Cedric Reichenbach |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Documentation update required: |
Yes
|
||||||||
| Epic Link: | Periscope back-end MVP | ||||||||
| Sprint: | Basel 160 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
User story:
Test Periscope/Find Bar performance with 300k+ content items. Generate stories, tours and assets. Run searches and time the responses. Background: Periscope search might be (too) slow as soon as we start dealing with more data, that is, many suppliers and many results per supplier. We should make sure that overall response time of a search stays within acceptable bounds - which should be at the magnitude of ~0.1 seconds to feel instantaneous for the user, or at least sub-second.
Acceptance criteria:
|