lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Tester <paulteste...@gmail.com>
Subject Re: solr asp.net integration challenge
Date Fri, 30 Nov 2012 10:07:17 GMT
Yes we do use paginating, we show 10 or 15 results but the user has an
option to select them all(count of the queryresult which is returned by
solr). When he uses this functionality we need all the selected doc id's(or
orginal primary keys from the database) in the asp.net application as fast
as possible. So i'm looking for a solution where the results(only the id's)
are shared between solr on tomcat and the asp.net application in IIS other
than over HTTP.



On Fri, Nov 30, 2012 at 2:48 AM, Gora Mohanty <gora@mimirtech.com> wrote:

> On 27 November 2012 21:19, Paul Tester <paultester01@gmail.com> wrote:
> > Hi all,
> >
> > At our company we have an asp.net webapplication hosted in IIS 7.5. This
> > application have a search module which is using solr. For communication
> > with the solr instance we use a 3th party plugin. For every search we
> show
> > the total count of the results and also 10 or 15 records. What we're now
> > trying to achieve is that the user can select all the records from his
> > search, which involves that all the doc ids should be available in the
> > asp.net application in IIS as fast as possible. Our problem is that the
> > count of his search easily can contain 1.000.000 records (or even more),
> > which takes way to long to transport them to the application via a json
> > result over http. So I'm looking for an alternative solution which is way
> > faster.
>
> Retrieving, and displaying, all of a million records is definitely
> going to be slow. Are you not paginating your displayed results?
> If so, you could fetch results from Solr in smaller batches, keeping
> a small window of pages around the current one.
>
> Regards,
> Gora
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message