On Wed, Mar 11, 2015 at 3:37 PM, Roberto De Ioris <[email protected]> wrote: > zeromq exposed file descriptor is edge triggered (you should find a bunch > of reference about it in the docs). So you must continue to read until > there is nothing more to read. Only after you are sure the queue is empty > you can start polling it again. > > This means you will not get a new poll event (even if there is some > message in the queue) if for that "round" an event has already been > generated.
That would explain things if it wasn't coming back from suspend when there were messages waiting, but my issue is the opposite... it's returning when there are _no_ messages. I can't remember if I mentioned it, but this only seems to happen immediately after calling uwsgi.wait_fd_read() and then uwsgi.suspend(). Meaning, I don't have suspend returning after waiting for a few seconds and then having nothing to read. Basically, it seems that the call to uwsgi.suspend() is failing to take control and context switch to another core. _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
