Sorry, write req/s was wrong. It is about 25,000, 12,500/s for each node.
On Wed, Jul 4, 2018 at 5:33 PM, 胡海麟 <[email protected]> wrote: > Hi, > > We use ignite as a redis server. > > The use case is > a. Write timeout is 15ms on the client side. > b. 2 server nodes. each is an EC2 r4.4xlarge instance. > c. Write req/s is about 120,000. In another word, 60,000 for each node. > > The problem is that timeout happens frequently, several ones per second. > A lower write req/s results less timeout. I guest we have bottleneck > somewhere. > > ========== > $ tail -f /opt/apache-ignite-fabric-2.5.0-bin/work/log/ignite-ee4f25ed.0.log > | grep pool > ^-- Public thread pool [active=0, idle=0, qSize=0] > ^-- System thread pool [active=0, idle=16, qSize=0] > ========== > system thread pool seems not busy at all. > > ========== > $ tail -f /opt/apache-ignite-fabric-2.5.0-bin/work/log/ignite-ee4f25ed.0.log > | grep "CPU " > ^-- CPU [cur=14.77%, avg=6.21%, GC=0%] > ^-- CPU [cur=13.43%, avg=6.23%, GC=0%] > ========== > CPU is not busy, either. > > We expected milli second level performance and we have too many timeout now. > Any idea for optimizing the performance? > > Thanks.
