Re: Ignite benchmarking with YCSB

Hello! Unfortunately there's not enoug info to be able to debug this further. I don't think you can get Ignite to use both IPs to connect client to server, unless you start two differing server nodes with different own IP. Regards, -- Sent from:

Re: Ignite benchmarking with YCSB

Hi Ilya, In early execution the writesyncmode=prim_sync was not set. I made this correction and enabled and able to get this performance. Even now CPU is not going above 50% in 3 node ignite cluster. network bandwidhth: 700 mbps rx and 350 tx. Not sure if there is any way now to improve above

Re: Ignite benchmarking with YCSB

Hello! Looks like your numbers have improved. What change would lead to such improvement? What's the current CPU utilization? Regards, -- Ilya Kasnacheev пн, 3 дек. 2018 г. в 12:48, summasumma : > HI Ilya, > > Thanks for all the inputs. > > Latest update is: > > Attempted Insert: 120k > 2

Re: Ignite benchmarking with YCSB

HI Ilya, Thanks for all the inputs. Latest update is: Attempted Insert: 120k 2 YCSB each with 80 threads giving: 54.5k / 54.5k = total 109k - Failed to touch target 120k - This is with Primary_Sync enabled in ignite but without Threadpool=64 or connection pair. Increasing System/Public

Re: Ignite benchmarking with YCSB

Hello! I'm afraid I have no idea anymore. Will it help if you decrease number of YCSB threads? Is it possible that YCSB uses the same key over and over again? Regards, -- Ilya Kasnacheev пт, 30 нояб. 2018 г. в 09:05, summasumma : > Hi Ilya, > > I have tried to set the following and rerun the

Re: Ignite benchmarking with YCSB

Hi Ilya, I have tried to set the following and rerun the same workload. But this time the performance got degraded from 56k Ops per YCSB to 47k Ops. PFA the thread dump with pairedconnection enabled: ycsb-1: ycsb1_dump1.ycsb1_dump1

Re: Ignite benchmarking with YCSB

Hello! It is hard to say what is the limiting factor here. Yes there's a lot of threads on YCSB side, but still a single one on Ignite side. And it's sitting on Communication write. Can you try doing the following: supplying custom TcpCommunicationSpi as ignite's communicationSpi with

Re: Ignite benchmarking with YCSB

Hi Ilya, Please find the YCSB side jstack threaddump files along with Ignite side. Please note that this time i have used 80 threads. Number of YCSBs: 2 Threads per YCSB: 80 YCSB-1 ThreadDump files on 2 occassions: ycsb1_load_1.ycsb1_load_1

Re: Ignite benchmarking with YCSB

Hello! I can see only one node actually doing any work, out of 6. I can see there's 100 threads on YCSB side, but it doesn't seem that there's actually any parallelism. Can you also do thread dump of YCSB? Regards, -- Ilya Kasnacheev чт, 29 нояб. 2018 г. в 16:20, summasumma : > Hi Ilya, > >

Re: Ignite benchmarking with YCSB

Hi Ilya, Yes i have taken during the workload and not before or after. Reattaching after fresh run now. Can u please check and let me know? load_1.load_1 load_2.load_2

Re: Ignite benchmarking with YCSB

Hello! I can't see any work happening in your thread dumps. Are you sure that you have collected them during your workload, as opposed to after load is finished (or before it is started)? Regards, -- Ilya Kasnacheev чт, 29 нояб. 2018 г. в 15:11, summasumma : > Hi Ilya, > > I have used jstack

Re: Ignite benchmarking with YCSB

Hi Ilya, I have used jstack to threaddump. PFA the dump files for your reference. These are taken after adding the following 64 Threadpool configuration in Apache Ignite configuration and while the Insert operation was happening with 55k OPS from YCSB: !-- Configure system thread pool.

Re: Ignite benchmarking with YCSB

Hello! No, you will have to use `jstack` or visualvm to get thread dump and then read it. It is human readable. Regards, -- Ilya Kasnacheev ср, 28 нояб. 2018 г. в 18:07, summasumma : > Thanks Ilya for the response. > > reg: "You will need to do thread dump mid-benchmark to see which thread >

Re: Ignite benchmarking with YCSB

Thanks Ilya for the response. reg: "You will need to do thread dump mid-benchmark to see which thread pools are full." --> can you please let me know if there is visor cli or command to check thread dump? Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite benchmarking with YCSB

Hello! I would start with tuning thread pool sizes if I see CPU under-loaded: https://apacheignite.readme.io/docs/thread-pools You will need to do thread dump mid-benchmark to see which thread pools are full. Regards, -- Ilya Kasnacheev чт, 22 нояб. 2018 г. в 20:28, summasumma : > Hi all,

Ignite benchmarking with YCSB

Hi all, I am trying to benchmark ignite with ycsb tool as follows: Ignite Cluster: 3 ignite-nodes each running in 1 VM (3 seperate VMs in cluster) VM details: -- CPU: 4 V-CPU (Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz) RAM: 16 Gb SSD: 40 GB Network: 1 Gb/s Apache