| www.informationclearinghouseinc.com
>
> Need Help? Click here to request IT Support.
>
>
> -Original Message-
> From: Walter Underwood [mailto:wun...@wunderwood.org]
> Sent: Wednesday, October 17, 2018 11:35 AM
> To: solr-user@lucene.apache.org
> Subject: Re
: Re: Solr performing Calculations vs. Pulling data Values Directly
>From DB Question
Instead of putting things in a database, I would put an HTTP cache, like
Varnish, in front of Solr. Then you get the best of both worlds. Fast fetches
for things that have already been calculated and results
port.
-Original Message-
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: Wednesday, October 17, 2018 11:30 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr performing Calculations vs. Pulling data Values Directly From
DB Question
On 10/17/2018 9:19 AM, Joseph Costello - F Rep
Instead of putting things in a database, I would put an HTTP cache, like
Varnish, in front of Solr. Then you get the best of both worlds. Fast fetches
for things that have already been calculated and results for any query that
shows up.
The client does not need special code to get the manually
On 10/17/2018 9:19 AM, Joseph Costello - F Reports wrote:
Any feedback from the group on the question below.
The question was will solr performing distance calculations (10,000++)
on the fly, perform faster than SQL query simply pulling
pre-calculated distance values directly from the
Any feedback from the group on the question below.
The question was will solr performing distance calculations (10,000++) on the
fly, perform faster than SQL query simply pulling pre-calculated distance
values directly from the database.
I know Solr is fast but basic computer science tells me
