Feature #6388


Compress Solr response for faster page load

Added by Lauren Walker over 10 years ago. Updated over 10 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Actions #1

Updated by Lauren Walker over 10 years ago

If the compression is not enough to decrease load time, move the abstract to a separate AJAX call after the rest of the information for the result list is retrieved.

Actions #2

Updated by ben leinfelder over 10 years ago

In the Apache config (mn-demo-8), I just tried adding:
AddOutputFilterByType DEFLATE text/json
and saw a reduction by a factor of about 4-5.

We can try it on KNB soon.

Actions #4

Updated by Lauren Walker over 10 years ago

It seems like the server takes about 1 - 1.2 seconds per query to send results to the client, no matter the query result size. Receiving on connections 1.5mb+ take less than 500ms to receive.

- Removing faceting reduces time by at least half
- Adding the query to the filter query (fq) parameter will allow us to take advantage of the filter cache

Actions #5

Updated by Lauren Walker over 10 years ago

  • Status changed from New to Resolved

I added filter queries so that we can start caching commonly used filters in Solr.

I also moved the faceted query to the end of our page load processes - so that now the regular query is sent and retrieved, results are added to the list and map, and then we send the faceted query and build the autocomplete dropdowns "in the background". There will be at least a 1 second delay between the page load and the autocomplete availability - but I don't foresee that being a huge issue since it takes about 1 second to click in the text input and start typing anyway.


Also available in: Atom PDF