Re: [jgroups-users] Getting high latency!!!

No, in fact you are correct. Because my cluster size is 113 not only 3. 3 for
ZK servers, 10 for the 10 machines that generate threads (senders) and 100
for threads (as each client has its own channel), note that only those (100
senders) are used for workload.
Doing this way it may be stupid. But there is a reason for choosing this
configuration. Because I need to keep all replay messages (from Zab
protocol) in client’s side for further check and more. 
Before, I had one channel for each 10 clients (senders), so, some replay
messages are lost when comes to Receive call back method because the Receive
method is not thread-safe (By the way, why Receive call back method is not
synchronized). When I override Receive method, I add synchronized code to
catch all replays inside the Receive method but it does not work for me. So
that is why I have for each sender its own channel. It could be more
sufficient solutions to remove such overhead channel.

<<The problem is that your thread pools below are too small to process 
<<this load and thus requests (and acks) get queued in the regular thread 
<<pool (queue size is 50'000) and the regular pool has a max of 8 threads. 
<<This introduces latency to each request, depending on how many requests 
<<are ahead of it in the queue.

I see what do you mean and it makes sense. However, I have tried your
suggestion, unfortunately there is no improvement. However, I have noticed
that when I have UDP default configuration (min thread pool = 2 and Max
thread pool = 8), the number of threads pool is always 2 (equals to its
minimum) because of min threads pool (the 2 threads) queue size is enough to
store the load (200 messages max at any given time, though), so UDP does not
need to create more than 2 thread pool. 

I really agree when you said the problem may be because of the messages are
queued and the latency depends on how many messages ahead in queue. And as
always we have only 2 threads pool during the workload time, this also
supporta your observation.

Moreover, I increased the number of thread pool to 200, 400 and 600 but this
also does not minimise the peak latencies.
I have more tries to do regarding to your suggestion I will tell you soon.
 

Ibrahim 




--
View this message in context: http://jgroups.1086181.n5.nabble.com/Getting-high-latency-tp11004p11008.html
Sent from the JGroups - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
javagroups-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/javagroups-users