hi all,

I have a trouble about huge message reading in my spout. that is the 
spout.nextTuple is called so slowly to read message from zmq like this: 
subscriber.recv(0);

it cause too many message accumulated at the zmq subscriber side, then the 
memory usage of this worker will grow up continually.

but when i try to use a pure java application based on jzmq to read the same 
zmq, it worked well. then i add an thread.sleep in my reading loop, the same 
problem appeared.

so, i think the cause is that spout.nextTuple is call too slowly, am i right? 
any suggestion?

Reply via email to