Hi, In a single server mode (embedded) there is no I/O (networking) at all. All the requests are executed locally. When you use the client node you’ll have I/O delays. The performance here can depend on several factors: - latency and throughput of your network; - CPU saturation;
So take a look at these system resources usage. Also make sure that there are no long GC pauses or that GC Threads don’t consume much of CPUs. Refer to this doc for JVM tuning settings https://apacheignite.readme.io/docs/jvm-and-system-tuning Finally, share your benchmark source and configuration for validation. — Denis > On Jun 16, 2016, at 11:04 PM, Pradeep Badiger <[email protected]> wrote: > > Hi, > > I am trying to run the yardstick ignite benchmark test on my local VM having > 8 Cores and 16GB RAM. I could see that the performance of Optimistic PUT/GET > is way low for a client-server mode than what I see when running within one > single server (embedded mode). Also the performance degrades with 1 > additional server node. Can someone help me to optimize this? > > There was a blog where the author commented that the performance of the > product is much similar when run in both client and server. Am I missing > something here? > > https://gridgain.blogspot.com/2015/04/benchmarking-data-grids-apache-ignite.html?showComment=1466104423051 > > <https://gridgain.blogspot.com/2015/04/benchmarking-data-grids-apache-ignite.html?showComment=1466104423051> > > > Thanks, > Pradeep V.B. > This email and any files transmitted with it are confidential, proprietary > and intended solely for the individual or entity to whom they are addressed. > If you have received this email in error please delete it immediately.
