On Feb 18, 2016, at 1:46 PM, Victor J. Orlikowski <[email protected]> wrote: > > 1) Cut the number of semaphores to 2 (PacketIns and "everything else").
This isn't going to work. I tried moving to a single priority queue and 2 semaphores (PacketIns, and "everything else") in our lab environment. I *immediately* saw an event timing issue, wherein EventDP arrived before SwitchFeatures, and broke an expectation in our application (that n_tables had been set, since our application is based on rest_router). I'm willing to try moving to something fewer than 3 semaphores - but eventlet's PriorityQueue is based on heapq. I'm not sure - but I *believe* that heapq maintains the heap invariant on the priorities - but is otherwise *not* FIFO - which might explain my need for a third semaphore. That having been said - if we're not getting events of the same priority in FIFO order due to the PriorityQueue - that's may not be a good thing. I will consider it further. Best, Victor -- Victor J. Orlikowski <> vjo@[cs.]duke.edu ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
