On Wednesday, March 11, 2015, Nick Kew <n...@apache.org> wrote: > On Wed, 2015-03-11 at 03:10 -0500, Brian Rectanus wrote: > > I certainly have some cycles if someone can help point me in the right > > direction. Right now I am at a loss as to where to dig. Profiler just > shows > > a lot of nothing (epoll) happening as you wrote. > > Hmmm. Is this with or without asynchronous notifications?
> This is with Master, not the new experimental code. > > I've been working on an experiment running Ironbee asynchronously > using a thread pool similar to the demo plugin. The issue that > concerns me most is that this approach requires rendezvous, > where the plugin needs to wait on notifications to determine > Continue vs Error in TxnReenable. > > I thought that might improve throughput despite potentially > blocking, because the txn thread is released in a cond_wait. > But I'd prefer a logic where I could proceed directly to > TxnReenable with neither Continue nor Error, but rather an > EAGAIN-like status and a same-phase callback to determine > Continue/Error when the rendezvous's condition is satisfied. > Does that make any sense? > > -- > Nick Kew > > -- Brian Rectanus
