On 12/6/22 07:53, Shawn Heisey wrote:
If Solr were a single-threaded application, this might make some
sense. But Solr is heavily multithreaded, there is no need to have
multiple nodes per machine to take full advantage of a multi-CPU
system. With multiple nodes, you're actually more likely t
On 12/6/22 05:08, Joe Jones (DHCW - Software Development) wrote:
Workaround tested and no difference with or without it. New cloud set up with
1200mb heap for each instance and 32gb system RAM on each server. I'm seeing
just over 20gb in system cache. Anti-virus exclusions applied and syste
information so we host in our own datacentres and
therefore can not make use of datadoghq.
-Original Message-
From: Jan Høydahl
Sent: 02 December 2022 18:47
To: users@solr.apache.org
Subject: Re: Solr 9.1 performance
WARNING: This email originated from outside of NHS Wales. Do not o
testing running the queries with "distrib=false" and can see
> the query itself runs fine it's just the call to the instance and the
> response is slow.
>
> Something to do with Jetty?
>
> -Original Message-
> From: Jan Høydahl
> Sent: 02 December 2
omething to do with Jetty?
-Original Message-
From: Jan Høydahl
Sent: 02 December 2022 10:14
To: users@solr.apache.org
Subject: Re: Solr 9.1 performance
WARNING: This email originated from outside of NHS Wales. Do not open links or
attachments unless you know the content is safe.
Coul
Could it be related to
https://solr.apache.org/news.html#java-17-bug-affecting-solr ? Doubt it as you
don't use much caching, but hotspot optimization of caches are disabled by
default in 9.1. You could try to edit bin/solr script to disable the patch and
see if anything is faster - risking a s
Hello all,
We currently have a Solr cloud set up under version 5.4.1 running on Windows.
It contains 45 million records in a collection split across 12 shards with a
replication factor of 2. The 12 shards are hosted across 6 servers running 4
nodes each. 3 servers are in one data center and 3
