Hi Rajan, could you please share the benchmark code with us? do you run queries against the same amount of records each time? what host machines do you use for your nodes? when you say that you have 5 nodes, does it mean that you use 5 dedicates machines for each node? Also, it might be that the benchmark itself is the bottleneck, so your system can handle more QPS, but you need to run a benchmark from several machines. Please try to use at least 2 hosts for the benchmark application and check if there any changes in QPS.
Thanks, Mike. On Thu, Jan 2, 2020 at 2:49 AM Rajan Ahlawat <rajan.ahla...@gmail.com> wrote: > > > ---------- Forwarded message --------- > From: Rajan Ahlawat <rajan.ahla...@gmail.com> > Date: Thu, Jan 2, 2020 at 4:05 PM > Subject: Ignite partitioned mode not scaling > To: <user@ignite.apache.org> > > > We are moving from replicated (1-node cluster) to multinode partitioned > cluster. > So assumption was that max QPS we can reach would be more if no. of nodes > are added to cluster. > We compared under 50ms QPS stats of partitioned mode with increasing no. > of nodes in cluster, and found that performance actually degraded. > We are using ignite key value as well as sql cache, where most of the data > in sql cache, no persistence is being used. > > please let us know what we are doing wrong or what can be done to make it > scalable. > here are the results of perf tests : > > *50ms in 95 percentile comparison of partitioned-mode* > > Response time in ms > cache mode (partitioned)QPSread from sql tableread from sql table with > joinread from sql table > 1-node 2600 48 46 47 > 3-node 2190 50 48 49 > 3-node-1-backup 2200 55 53 54 > 5-node 2000 54 52 53 > 5-node-2-backup 1990 51 49 50 > -- Thanks, Mikhail.
