[MGNLPER-59] Check performance of periscope, limit results Created: 29/Oct/18 Updated: 09/Nov/18 Resolved: 09/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: | Ilgun Ilgun |
| 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
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Periscope back-end MVP | ||||||||
| Sprint: | Basel 159 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
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.
|