I was stumbling around the code and found a out_batch_size in config.hpp. I wonder what would happen if I lower that value. :-)
A hint is better than nothing, I suppose. I don't mind that it's getting sent out in the background I/O as soon as possible without a hard guarantee at the app thread. Just want to make sure that the data is not hanging around for a long time before it decides that it's "too long". I tried inserting a sleep in my sender application thread hoping that it'd give the IO thread time to send out the content in the buffer, but it won't don't it. The app thread slept as long as 15 secs. Chris On Apr 15, 2010, at 5:59 PM, Martin Lucina wrote: > [email protected] said: >> Ah shoot. I really need that. I'll try to resurrect it. What would be a >> good alternative name for it? >> >> Maybe it should come back as a socket option? >> >> Thoughts? > > The original zmq_flush() and the accompanying ZMQ_NOFLUSH flag to send was > really more of a hint to the 0MQ core saying "You want to flush this now" > rather than a strict disabling of batching per se. I'm not sure if the > latter is possible at all, you'll want Martin Sustrik's opinion on that. > > -mato > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
