>> Maybe check the CPU load on your server machine and/or run a (java) >> profiler. >> Except the "unusual" buffer size you have chosen (maybe you have a good >> reason for that?!), I don't see any issues. > > > I don't think that the chosen buffer size are "unusual". If you are going to > transfer large amount of data, this is quite sane to use large buffers.That > being said, it all depends on what you do when you process an incoming > message. > > Also check that the pb is not on your injector : are you sending enough > message to saturate your server ? >
When the client receives the incoming message it issues new server query. It does not issue the next query until a response on previous query is received. It does nothing with the response. The goal is to check the maximum IO possible and number of clients. Currently we test only with 1-10 clients (and we have resources to do more, but ran into the low IO with this set up). We have currently 3 sizes of messages, the biggest one is 1 MB. The CPU is surely not loaded. Munin live statistics shows not more than 400K output traffic per 0.5 sec. from the server. We ran some tests on our network and they showed about 500 Mb/sec mean speed. Thus, the network is not saturated with our server Also it is interesting that when we increase the buffer size the number of MESSAGE_RECEIVED events does not noticably changes at client or speed increases. > Also check that the pb is not on your injector : are you sending enough > message to saturate your server ? What do you mean by "pb" and "injector"?
