December 14, 2012
On Monday, 10 December 2012 at 23:04:56 UTC, Nick B wrote:
> On Monday, 10 December 2012 at 20:08:32 UTC, Andrei Alexandrescu wrote:
>> On 12/9/12 10:58 PM, Nick B wrote:
>> [about the Disruptor framework]
>>> Would Andrei like to comment on any of the comments so far ??
>>
>> Sorry, I'd need to acquire expertise in Disruptor before discussing it. I found http://disruptor.googlecode.com/files/Disruptor-1.0.pdf quite difficult to get into because it spends the first page stating how good Disruptor is, then the next 3 pages discussing unrelated generalities, to then start discussing implementation details still without really defining the pattern. I had to stop there.
>>
>> Is there a more concise description of the pattern?
>>
>>
>> Andrei
>
> I have looked, but I think the answer is to this question is no.
>
> Nick

Correction. The answer to this question is actually YES.
Read the martinfowler article. See the link below.

see Dmitry comments below, as well as  I'd consider

[Dmitry comments] http://martinfowler.com/articles/lmax.html to be quite nice
description as it helped me to decipher the most of details.
The paper itself lacks illustrative material, focuses too much on
overcoming Java limitations and generally too terse with important (to
me) details of the framework.

Totally agree.

Nick


December 14, 2012
On Fri, 2012-12-14 at 05:19 +0100, Nick B wrote:
[…]
> Correction. The answer to this question is actually YES. Read the martinfowler article. See the link below.
[…]

Whilst the Martin Fowler article is a good one, it is an analysts perspective on it given some study. Can I suggest that people interested in The Disruptor read the material of Trisha Gee, Mike Barker, and others. They worked on the system and have done the JavaOne, Devoxxx, JAXLondon, etc. circuit making many presentation on this from the ring buffer datastructure down to how ensuring cache line coherence on the processors influenced the way they wrote their Java code to make things lock free. Trisha has now moved on from LMAX to MongoDB, so is no longer doing The Disruptor talks.  but her blog is basically an index to materials.

And of course The Disruptor is FOSS, the code is on GitHub for people to look at.

https://github.com/LMAX-Exchange/disruptor

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


December 16, 2012
On Wednesday, 12 December 2012 at 08:09:40 UTC, Dmitry Olshansky wrote:
> 12/12/2012 6:00 AM, Nick B пишет:
>> On Monday, 10 December 2012 at 23:04:56 UTC, Nick B wrote:
>>> On Monday, 10 December 2012 at 20:08:32 UTC, Andrei Alexandrescu wrote:
>>>> On 12/9/12 10:58 PM, Nick B wrote:
>>>> [about the Disruptor framework]
>>>>> Would Andrei like to comment on any of the comments so far ??
>>>>
>>>> Sorry, I'd need to acquire expertise in Disruptor before discussing
>>>> it. I found http://disruptor.googlecode.com/files/Disruptor-1.0.pdf
>>>> quite difficult to get into because it spends the first page stating
>>>> how good Disruptor is, then the next 3 pages discussing unrelated
>>>> generalities, to then start discussing implementation details still
>>>> without really defining the pattern. I had to stop there.
>>>>
>>>> Is there a more concise description of the pattern?
>>>>
>>>>
>>
>> Ok, does anyone consider that this pattern, though not well described,
>> has any value ?
>>
>> Nick
>
> It surely has.
>
> I'd consider http://martinfowler.com/articles/lmax.html to be quite nice description as it helped me to decipher the most of details.
> The paper itself lacks illustrative material, focuses too much on overcoming Java limitations and generally too terse with important (to me) details of the framework.

[Request again] Would Andre like to make any comment, especially on the martin fowler article ? Others commenting here have said that they consider that the pattern has some value ?

Nick
December 16, 2012
On 12/16/12 4:28 AM, Nick B wrote:
>> I'd consider http://martinfowler.com/articles/lmax.html to be quite
>> nice description as it helped me to decipher the most of details.
>> The paper itself lacks illustrative material, focuses too much on
>> overcoming Java limitations and generally too terse with important (to
>> me) details of the framework.
>
> [Request again] Would Andre like to make any comment, especially on the
> martin fowler article ? Others commenting here have said that they
> consider that the pattern has some value ?

What I think about a paper upon first sight is unlikely to be all that insightful, and I already have a long reading list. Why do you find it so important? Are you considering proposing a pattern implementation for Phobos and would like to gauge initial interest?


Thanks,

Andrei

December 16, 2012
On Sunday, 16 December 2012 at 14:58:46 UTC, Andrei Alexandrescu wrote:
>> [Request again] Would Andre like to make any comment, especially on the
>> martin fowler article ? Others commenting here have said that they
>> consider that the pattern has some value ?
>
> What I think about a paper upon first sight is unlikely to be all that insightful, and I already have a long reading list. Why do you find it so important? Are you considering proposing a pattern implementation for Phobos and would like to gauge initial interest?
>
>
> Thanks,
>
> Andrei

>   Are you considering proposing a pattern implementation for
Phobos and would like to gauge initial interest?

Yes I am interested to see if there is  ommunity interest in this pattern, and also if it could in included in Phobos, some time in the future.

Nick
Next ›   Last »
1 2 3
Top | Discussion index | About this forum | D home