You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using zmq inproc socket to transmit messages between threads. we have set Hwm accordingly and using multipart message, i.e send() method with the necessary flag. We are seeing this behavior of large memory consumption when large amount of messages are being transmitted using this socket, the usage is outsize heap. I looked into the page-fault graph and can see that most of the page-fault is created by java_org_zeromq_SocketSend , I tried to trace native allocation using jemalloc and the output obtained also suggest large allocation during SocketSend. From jemalloc output I can see that leak might be associated with zmq msg_t initsize() function. I have attached graph of what I have described above. I tried to use ZMsg.send() along with destroy flag set , but no change in the memory usage pattern. Can someone help me how to tackle the issue.
The text was updated successfully, but these errors were encountered:
We are using zmq inproc socket to transmit messages between threads. we have set Hwm accordingly and using multipart message, i.e send() method with the necessary flag. We are seeing this behavior of large memory consumption when large amount of messages are being transmitted using this socket, the usage is outsize heap. I looked into the page-fault graph and can see that most of the page-fault is created by java_org_zeromq_SocketSend , I tried to trace native allocation using jemalloc and the output obtained also suggest large allocation during SocketSend. From jemalloc output I can see that leak might be associated with zmq msg_t initsize() function. I have attached graph of what I have described above. I tried to use ZMsg.send() along with destroy flag set , but no change in the memory usage pattern. Can someone help me how to tackle the issue.
The text was updated successfully, but these errors were encountered: