User story:

I have around 300k stories in the Stories app. They are stored in the JCR. Have you tested Find Bar with these amounts? (real question from a partner)

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.

• Check the performance of Periscope when dealing with reasonably large data
• Limit the maximum number of items listed per supplier (e.g. 5 items) and as many suppliers as to be expected in a typical customer setup.

Acceptance criteria:

• Response time stays under 1 second.
• Come up with mitigations for found bottlenecks and either directly apply them or create follow-up tickets.
• Propose recommendations on how clients should set up search indexing for good performance.
  • When/with how many items is Jackrabbit/Lucene search OK?
  • When/with how many items is Solr needed?
  • How to configure Find Bar / Periscope for optimal performance?