On Wed, 2013-01-16 at 07:50 +0100, Mladen Turk wrote: > On 01/15/2013 02:29 PM, Mark Thomas wrote: > > Hi, > > > > 3. Currently, we have no record of which Poller a socket is registered > > with. This makes 2) more expensive as we have to iterate through the > > Pollers to find the socket. Tracking the current poller used by a socket > > would make 2) a cheaper operation. > > Think this can be done with relative ease. > I recently made some changes to native pollset performance > (removing multiple linear scans for sockets if they are in the pollset) > which can reference the pollset with socket. > > In theory this allows to remove the socket from 'any' pollset which > means that you can remove the socket from pollset without knowing to > which one it belongs. > > If there is a need for reconfigure (different signaling events) > we can add an extra API call that would allow that, without the need > to know for which pollset this is.
Yes, remove [and add as well, but hopefully this was never a big issue] performance is essential, because write events mean more events, and flags also need to be updated. So a lot more operations overall. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
