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, I’d say 100% CPU utilization is not a good place to be in. It’s a almost guarantee for a resource starvation.
So, one should distinguish those type of workloads. Also there is universal kind of recipe for those situations. Run a JVM profiler/sampler (JMC, for example) and look where this time is spent. It might have been GC. > On Jan 4, 2017, at 18:05, Adrien Grand <jpou...@gmail.com> wrote: > > Well, you could but that would not make sense, 100% CPU usage is really the > best you can get. Why would you like to make things worse artificially? --- Denis Bazhenov <dot...@gmail.com>
