We being new to Lucene are struggling hard to dimension our application
w.r.t search throughput
As stated by "Mike McCandless" in the following thread, we had ran our
cases with restrictive data set also.
http://mail-archives.apache.org/mod_mbox/lucene-java-user/201701.mbox/raw/%3CCAL8Pwka4RC3c%2B%
I know when I first came to Lucene and ran some tests/benchmarks on
indexing and searching, I was surprised at how high the CPU usage was - I
could easily saturate an 8 or 16 CPU system. I expected it to be strongly
IO-bound and I've heard others express that surprise when they first learn
about it
One should really put things in context. If those searches are some kind of
background workload (no users are waiting for search results), I’ll agree 100%
CPU utilization is kind of ideal situation. But if we’re speaking of
interactive system where there is user waiting behind each search query,
Le mer. 4 janv. 2017 à 06:55, Rajnish kamboj a
écrit :
> Might be you are right as we are running our system under load test so we
> are firing 200 requests with JMeter (loop forever). This may be the cause
> of 100% CPU usage with 4 vCPUs machine.
> In this case should we manually restrict our L
@Evert
We have 16 GB total RAM, out of which Heap is using 4 GB.
Initially we use RAMDirectory, but later switched to MMapDirectory since
RAMDirectory is not meant for production use.
@Adrien
Might be you are right as we are running our system under load test so we
are firing 200 requests with JMe
Are you running search requests in a loop from more than 4 threads? If yes
then this situation is ideal like Trejkaz said. Otherwise please describe
your workload and explain why you think 100% CPU usage is not ideal.
Le mar. 3 janv. 2017 à 12:52, Rajnish kamboj a
écrit :
> High CPU may be ideal
4 Gb RAM for 4 CPU's may be too small. Try to increase the RAM to 16 Gb and
load the Index in RAMDisk. That may help.
Op di 3 jan. 2017 om 12:52 schreef Rajnish kamboj
> High CPU may be ideal, but 100% CPU utilization is not ideal. (We might be
>
> missing very silly thing)
>
>
>
> More inform
High CPU may be ideal, but 100% CPU utilization is not ideal. (We might be
missing very silly thing)
More information on our environment:
Machine details: 4 vCPUs and 4 GB RAM
Search Load: ~200 simultaneous users searching requests.
Data set : 3.5 Million records (~ 2 GB index size).
We reduced o
On Tue, Jan 3, 2017 at 5:26 AM, Rajnish kamboj wrote:
>
> Hi
>
> The CPU usage goes upto 100% during search.
Isn't that ideal? Or would you prefer your searches to be slow, blocked by I/O?
TX
-
To unsubscribe, e-mail: java-user
Hi
The CPU usage goes upto 100% during search.
We were using RAM Directory, but later switched to MMap Directory.
The CPU usage remains between 90-100%.
Is it obvious that the CPU usage remain high during Lucene search or we are
missing something?
Our data set was only 3.5 Million records (~ 2 G
10 matches
Mail list logo
