On 1/11/2018 11:50 AM, Shashank Pedamallu wrote:
> Thank you for the reply Kevin. I was using 6 vms from our private cloud. 5
> among them, I was using as clients to ingest data on 5 independent cores. One
> vm is hosting the Solr which is where all ingest requests are received for
> all cores.
Thank you for the reply Kevin. I was using 6 vms from our private cloud. 5
among them, I was using as clients to ingest data on 5 independent cores. One
vm is hosting the Solr which is where all ingest requests are received for all
cores. Since they are all on same network, I think they should n
When you say "multiple machines", was these all local machines or vms or
something else? I worked with a group once that used laptops to benchmark a
service and it was a WiFi network limit that caused weird results. LAN
connections or even better a dedicated client machine would help push more
docu
Thank you very much for the reply Shawn. Is the jmeter running on a different
machine from Solr or on the same machine?
Solr is running on a dedicated VM. And I’ve tried to split the client requests
from multiple machines but the result was not different. So, I don’t think the
bottleneck is with
On 1/10/2018 12:58 PM, Shashank Pedamallu wrote:
As you can see, the number of documents being ingested per core is not scaling
horizontally as I'm adding more cores. Rather the total number of documents
getting ingested for Solr JVM is being topped around 90k documents per second.
I would ca
They are separate cases. In attempt 1 – I was ingesting to only 1 core. Then to
3 cores and then 5 cores. Yes, they are completely independent cores.
I think I was not reading the ‘iostats’ right. With –x option, the ‘avgrq-sz’
parameter is constantly above 300. From some readings online, I see
OK, so I'm assuming your indexer indexes to 1, 3 and 5 separate cores
depending on how many are available, right? And these cores are essentially
totally independent.
I'd guess your gating factor is your ingestion process. Try spinning up two
identical ones from two separate clients. Eventually yo
- Did you sept up an actual multiple node cluster or are you running this all
on one box?
Sorry, I should have mentioned this earlier. I’m running Solr in non-cloud
mode. It is just a single node Solr.
- Are you configuring Jmeter to send with multiple threads?
Yes, multiple threads looping a fi
And I'd add
- are you sending one document at a time or batching them up? See:
https://lucidworks.com/2015/10/05/really-batch-updates-solr-2/
Best,
Erick
On Wed, Jan 10, 2018 at 1:35 PM, Gus Heck wrote:
> Ok then here's a few things to check...
>
>- Did you sept up an actual multiple node c
Ok then here's a few things to check...
- Did you sept up an actual multiple node cluster or are you running
this all on one box?
- Are you configuring Jmeter to send with multiple threads?
- Are they all sending to the same node, or are you distributing across
nodes? Is there a loa
Hi Gus,
Thank for the reply. I’m sending via jmeter running on my local machine to
Solr running on a remote vm.
Thanks,
Shashank
On 1/10/18, 12:34 PM, "Gus Heck" wrote:
Ingested how? Sounds like your document sending mechanism is maxed, not the
solr cluster...
On Wed, Jan 10
Ingested how? Sounds like your document sending mechanism is maxed, not the
solr cluster...
On Wed, Jan 10, 2018 at 2:58 PM, Shashank Pedamallu
wrote:
> Hi,
>
>
>
> I’m trying to find the upper thresholds of ingestion and I have tried the
> following. In each of the experiments, I’m ingesting ra
12 matches
Mail list logo
