OK, this makes very little sense. The individual queries are taking < 100ms yet the total response is 29 seconds. I do note that one of your queries has rows=1010, a typo?
Anyway, not at all sure what's going on here. If these are gigantic files you're returning, then it could be decompressing time, unlikely but possible. Try again with rows=0&start=1000 to see if it's something weird with getting the stored data, but that's highly doubtful. I think the only real way to get to the bottom of it will be to slap a profiler on it and see where the time is being spent. Best, Erick On Fri, Oct 9, 2015 at 9:53 AM, Toke Eskildsen <t...@statsbiblioteket.dk> wrote: > Salman Ansari <salman.rah...@gmail.com> wrote: >> Thanks Eric for your response. If you find pagination is not the main >> culprit, what other factors do you guys suggest I need to tweak to test >> that? > > Well, is basic search slow? What are your response times for plain un-warmed > top-20 searches? > >> As I mentioned, by navigating to 20000 results using start and row I >> am getting time out from Solr.NET and I need a way to fix that. > > You still haven't answered my question: Do your users actually need to page > that far? > > > Again: I know there can be 10 million results. Why would your users need to > page through all of them? Why would they need to page trough just the first > 1000? What are they trying to achieve? > > If they used it automatically for full export of the result set, then I can > understand it, but you talked about next & previous page, which indicates > that this is a manual process. A manual process that requires clicking next > 1000 times is a severe indicator that something can be done differently. > > - Toke Eskildsen
