[Opentnl-general] Memory explodes while sending TNL::BytebufferPtr
Brought to you by:
mark_frohnmayer,
s_alanet
From: Jan F. <jan...@gm...> - 2007-01-24 00:37:07
|
Hello, i use the tnl for a project which i develop for my diploma thesis. My plan is to implement a server which only dispatches messages between clients an a server grid. Therefore i use the Eventconnection with some RPC s. The data i recive from the clients (or servers) is encoded in a ByteBuffer (TNL::ByteBufferPtr) and i dont want to decode it on the dispatch server. So is call another rpc with the same buffer that it sends to the remote client. That works. Clients and servers recives the right messages. But when i look at the memory usage of my applikation then i see that it grows very quickly. Especialy when i send huge amount of messages. In my testcase there are 20 clients which sends 10 messages per second. Every message is 8 byte . So my question is: are there some limitations of RPC so that i cant handle this amount of messages. I have tested a little bit and for me it seems that either the refcount of the BufferPtr will not decrease that i can deleted or the memory of the created Events will not freed. Have anyone some experience with sending bytebuffers very often? Cheers Jan |