Hi Toke,

Also, if it helps, the content on each server is between around 6.2Gb and
7.8Gb.

Thanks,

Russ

*Manzama*a MODERN GOVERNANCE company

Russell Bahr
Lead Infrastructure Engineer

USA & CAN Office: +1 (541) 306 3271
USA & CAN Support: +1 (541) 706 9393
UK Office & Support: +44 (0)203 282 1633
AUS Office & Support: +61 (0) 2 8417 2339

543 NW York Drive, Suite 100, Bend, OR 97703

LinkedIn <http://www.linkedin.com/company/manzama> | Twitter
<https://twitter.com/ManzamaInc> | Facebook
<http://www.facebook.com/manzamainc> | YouTube
<https://www.youtube.com/channel/UCBo3QoqewyNoo7HiT_BFuRw>


On Tue, Sep 3, 2019 at 12:22 PM Russell Bahr <r...@manzama.com> wrote:

> Hi Toke,
>
> Yes, some of our queries are quite complex due to a lot of very specific
> positive as well as negative boosts, however, the query that I ran as the
> base test after we found our queries were taking so long is just "
> http://solr.obscured.com:8990/solr/content/select?q=*%3A*&wt=json&indent=true
> "
>
> Our index sizes run between 12k to 36k per server
>
>
>
> *Manzama*a MODERN GOVERNANCE company
>
> Russell Bahr
> Lead Infrastructure Engineer
>
> USA & CAN Office: +1 (541) 306 3271
> USA & CAN Support: +1 (541) 706 9393
> UK Office & Support: +44 (0)203 282 1633
> AUS Office & Support: +61 (0) 2 8417 2339
>
> 543 NW York Drive, Suite 100, Bend, OR 97703
>
> LinkedIn <http://www.linkedin.com/company/manzama> | Twitter
> <https://twitter.com/ManzamaInc> | Facebook
> <http://www.facebook.com/manzamainc> | YouTube
> <https://www.youtube.com/channel/UCBo3QoqewyNoo7HiT_BFuRw>
>
>
> On Tue, Sep 3, 2019 at 10:54 AM Toke Eskildsen <t...@kb.dk> wrote:
>
>> Russell Bahr <r...@manzama.com> wrote:
>> > approximately 18 million documents
>> > *:* query across 10 times returning
>> > [13234, 18714, 13384, 12966, 12192, 18420, 16592, 15691, 13373, 12458]
>> >vs
>> > [93359, 94263, 86949, 90747, 91171, 91588, 87921, 88632, 88035, 89137]
>>
>> Even the 12-18 seconds for Solr 4 is a long time, so I'm guessing that
>> your queries are complex, you are asking for large result sets, heavy
>> aggregations or something like that. Can you provide the full list of
>> parameters in your request?
>>
>> Related, 30 machines to handle 18 million documents sounds like a lot.
>> Are you serving very large documents? How big is your index in bytes?
>>
>> - Toke Eskildsen
>>
>

Reply via email to