Re: Question about async logger wait strategies

2016-06-14 Thread Anthony Maire
If the sources have not been moved, it's still considered as experimental on master (and it was still experimental on 3.3.5-rc2 tag) https://github.com/LMAX-Exchange/disruptor/blob/master/src/main/java/com/lmax/disruptor/LiteBlockingWaitStrategy.java 2016-06-14 7:15 GMT+02:00 Gary Gregory

Re: Question about async logger wait strategies

2016-06-13 Thread Gary Gregory
On Mon, Jun 13, 2016 at 9:51 PM, Anthony Maire wrote: > Basically you want a logging framework to have as little impact as possible > on the application. That's why the sleeping strategy is a good > general-purpose choice : no allocation, no lock for the application >

Re: Question about async logger wait strategies

2016-06-13 Thread Anthony Maire
Basically you want a logging framework to have as little impact as possible on the application. That's why the sleeping strategy is a good general-purpose choice : no allocation, no lock for the application threads, and a CPU consumption when "idle" that will stay pretty low on most OS (it roughly

Re: Question about async logger wait strategies

2016-06-13 Thread Remko Popma
Currently there isn't but there's no real reason not to. That reminds me we should add LiteBlocking (a standard Disruptor wait strategy). Sent from my iPhone > On 2016/06/14, at 5:50, Matt Sicker wrote: > > Also, is there a way to specify a custom WaitStrategy, or is that

Re: Question about async logger wait strategies

2016-06-13 Thread Remko Popma
The busy-spin wait strategy is not something I want to promote since it basically dedicates a full core to the logging background thread. It's there mostly for testing and perhaps for hardcore users who are familiar with the Disruptor. Sent from my iPhone > On 2016/06/14, at 3:24, Matt

Re: Question about async logger wait strategies

2016-06-13 Thread Matt Sicker
Also, is there a way to specify a custom WaitStrategy, or is that pointless? On 13 June 2016 at 13:24, Matt Sicker wrote: > The code has a case for the busy spin strategy, but it's not listed on > this page: . Is > this

Question about async logger wait strategies

2016-06-13 Thread Matt Sicker
The code has a case for the busy spin strategy, but it's not listed on this page: . Is this unsupported or should it be added to the docs? -- Matt Sicker