A Java Fork-Join Calamity

Hadn't seen this before, so I thought I'd share. Comments are very welcome.
http://coopsoft.com/ar/CalamityArticle.html

RE: A Java Fork-Join Calamity

Added by Chris Marshall on 2012-02-13, 12:01
This serves excellently to illustrate the point that skimping on paying a proper technical writer is a false economy.

From: nilskp [at] gmail [dot] com
Date: Fri, 10 Feb 2012 23:07:50 -0500
Subject: [scala-user] A Java Fork-Join Calamity
To: scala-user [at] googlegroups [dot] com

Hadn't seen this before, so I thought I'd share. Comments are very welcome.
http://coopsoft.com/ar/CalamityArticle.html

Re: A Java Fork-Join Calamity

Added by Rikolino on 2012-02-13, 12:31

Probably like blue-ribbon for fastest ship from Europe to USA.

Re: A Java Fork-Join Calamity

Added by Viktor Klang on 2012-02-13, 13:31
I think he means this: http://en.wikipedia.org/wiki/Blue_ribbon

On Mon, Feb 13, 2012 at 12:27 PM, Rikolino <riko [dot] noc [at] gmail [dot] com> wrote:
Probably like blue-ribbon for fastest ship from Europe to USA.



--
Viktor Klang

Akka Tech LeadTypesafe - The software stack for applications that scale

Twitter: @viktorklang

Re: A Java Fork-Join Calamity

Added by Viktor Klang on 2012-02-16, 11:21

I thought this could be of interest:
http://www.dzone.com/links/scalability_of_akka_20_fork_join_pool_48_core...

Cheers,
√

2012/2/13 √iktor Ҡlang :
> I think he means this: http://en.wikipedia.org/wiki/Blue_ribbon
>
>
> On Mon, Feb 13, 2012 at 12:27 PM, Rikolino wrote:
>>
>> Probably like blue-ribbon for fastest ship from Europe to USA.
>
>
>
>
> --
> Viktor Klang
>
> Akka Tech Lead
> Typesafe - The software stack for applications that scale
>
> Twitter: @viktorklang
>

Re: A Java Fork-Join Calamity

Added by nilskp on 2012-02-16, 16:31
On Thu, Feb 16, 2012 at 4:08 AM, √iktor Ҡlang <viktor [dot] klang [at] gmail [dot] com> wrote:
I thought this could be of interest:
http://www.dzone.com/links/scalability_of_akka_20_fork_join_pool_48_core_ser.html

Cheers,
√

:-) 

2012/2/13 √iktor Ҡlang <viktor [dot] klang [at] gmail [dot] com>:
> I think he means this: http://en.wikipedia.org/wiki/Blue_ribbon
>
>
> On Mon, Feb 13, 2012 at 12:27 PM, Rikolino <riko [dot] noc [at] gmail [dot] com> wrote:
>>
>> Probably like blue-ribbon for fastest ship from Europe to USA.
>
>
>
>
> --
> Viktor Klang
>
> Akka Tech Lead
> Typesafe - The software stack for applications that scale
>
> Twitter: @viktorklang
>



--
Viktor Klang

Akka Tech Lead
Typesafe - The software stack for applications that scale

Twitter: @viktorklang

Re: A Java Fork-Join Calamity

Added by milessabin on 2012-02-11, 10:51

On Sat, Feb 11, 2012 at 4:07 AM, Nils Kilden-Pedersen wrote:
> Hadn't seen this before, so I thought I'd share. Comments are very welcome.
>
> http://coopsoft.com/ar/CalamityArticle.html

One comment: Clueless troll alert ...

"If only the lightweight F/J Framework were a blue-ribbon application
server. Regrettably, the framework is not a professional application
server."

Nuff said ...

Cheers,

Miles

Re: A Java Fork-Join Calamity

Added by Stefan Zeiger on 2012-02-13, 11:11

On 2012-02-11 10:33, Miles Sabin wrote:
> "If only the lightweight F/J Framework were a blue-ribbon application
> server. Regrettably, the framework is not a professional application
> server." Nuff said ...

Blue-ribbon application server? What's that supposed to be? (The first
google hit for the term is his article)

-sz

Re: A Java Fork-Join Calamity

Added by Naftoli Gugenheim on 2012-02-13, 11:21
I think it means, something that meets all the criteria he came up with (by making a comparison of FJ vs. his product).

On Mon, Feb 13, 2012 at 5:00 AM, Stefan Zeiger <szeiger [at] novocode [dot] com> wrote:
On 2012-02-11 10:33, Miles Sabin wrote:
"If only the lightweight F/J Framework were a blue-ribbon application server. Regrettably, the framework is not a professional application server." Nuff said ...

Blue-ribbon application server? What's that supposed to be? (The first google hit for the term is his article)

-sz

Re: A Java Fork-Join Calamity

Added by d_m on 2012-02-11, 16:41

On Sat, Feb 11, 2012 at 09:33:12AM +0000, Miles Sabin wrote:
> One comment: Clueless troll alert ...
>
> "If only the lightweight F/J Framework were a blue-ribbon application
> server. Regrettably, the framework is not a professional application
> server."
>
> Nuff said ...

Also, dude did not disclose that in fact his professional work involves
selling a "professional application server that does fork/join": the
one mentioned in the article (without saying it's his project).

See "Tymeac" at http://coopsoft.com/Products.html

It's fine to diss competing products/libraries/whatever but sketchy not
to disclose your own situation in the article, IMO anyway.

Re: A Java Fork-Join Calamity

Added by Maxime Lévesque on 2012-02-11, 17:01

I tried again, trying not to be biased by the powerful rhetoric :disqualification  by "lack of industry professional attributes", and by  "failure to be a blue ribbon app server". The quality of the substance seems the same as that of the rhetoric....

2012/2/11 Erik Osheim <erik [at] plastic-idolatry [dot] com>
On Sat, Feb 11, 2012 at 09:33:12AM +0000, Miles Sabin wrote:
> One comment: Clueless troll alert ...
>
> "If only the lightweight F/J Framework were a blue-ribbon application
> server. Regrettably, the framework is not a professional application
> server."
>
> Nuff said ...

Also, dude did not disclose that in fact his professional work involves
selling a "professional application server that does fork/join": the
one mentioned in the article (without saying it's his project).

See "Tymeac" at http://coopsoft.com/Products.html

It's fine to diss competing products/libraries/whatever but sketchy not
to disclose your own situation in the article, IMO anyway.

Re: A Java Fork-Join Calamity

Added by Viktor Klang on 2012-02-11, 16:41

To me the entire post is just FUD.
The new ForkJoinPool has much better scalability than ThreadPoolExecutor.
Also, Akka uses it exclusively for async tasks (no joining) with
remarkable performance.

And, if you've ever looked inside the java.util.concurrent.* sources
before, you know you have to write unorthodox code to get things done
with low overhead.

Cheers,
√

On Sat, Feb 11, 2012 at 4:31 PM, Erik Osheim wrote:
> On Sat, Feb 11, 2012 at 09:33:12AM +0000, Miles Sabin wrote:
>> One comment: Clueless troll alert ...
>>
>> "If only the lightweight F/J Framework were a blue-ribbon application
>> server. Regrettably, the framework is not a professional application
>> server."
>>
>> Nuff said ...
>
> Also, dude did not disclose that in fact his professional work involves
> selling a "professional application server that does fork/join": the
> one mentioned in the article (without saying it's his project).
>
> See "Tymeac" at http://coopsoft.com/Products.html
>
> It's fine to diss competing products/libraries/whatever but sketchy not
> to disclose your own situation in the article, IMO anyway.
>

Re: A Java Fork-Join Calamity

Added by nilskp on 2012-02-11, 17:21
On Sat, Feb 11, 2012 at 10:36 AM, √iktor Ҡlang <viktor [dot] klang [at] gmail [dot] com> wrote:
To me the entire post is just FUD.
The new ForkJoinPool has much better scalability than ThreadPoolExecutor.
Also, Akka uses it exclusively for async tasks (no joining) with
remarkable performance.

And, if you've ever looked inside the java.util.concurrent.* sources
before, you know you have to write unorthodox code to get things done
with low overhead.

Absolutely. This, probably more than anything, was an idiotic point.

Re: A Java Fork-Join Calamity

Added by nilskp on 2012-02-11, 16:21
On Sat, Feb 11, 2012 at 4:33 AM, Miles Sabin <miles [at] milessabin [dot] com> wrote:
On Sat, Feb 11, 2012 at 4:07 AM, Nils Kilden-Pedersen <nilskp [at] gmail [dot] com> wrote:
> Hadn't seen this before, so I thought I'd share. Comments are very welcome.
>
> http://coopsoft.com/ar/CalamityArticle.html

One comment: Clueless troll alert ...

"If only the lightweight F/J Framework were a blue-ribbon application
server. Regrettably, the framework is not a professional application
server."

Nuff said ...

So, are you saying that it IS an application server? Or are you saying that it shouldn't be considered an application server?
I too thought it was a weird statement to make when I read the piece, but isn't there a valid point in there somewhere?

Re: A Java Fork-Join Calamity

Added by milessabin on 2012-02-11, 16:51

On Sat, Feb 11, 2012 at 3:13 PM, Nils Kilden-Pedersen wrote:
> On Sat, Feb 11, 2012 at 4:33 AM, Miles Sabin wrote:
>>
>> On Sat, Feb 11, 2012 at 4:07 AM, Nils Kilden-Pedersen
>> wrote:
>> > Hadn't seen this before, so I thought I'd share. Comments are very
>> > welcome.
>> >
>> > http://coopsoft.com/ar/CalamityArticle.html
>>
>> One comment: Clueless troll alert ...
>>
>> "If only the lightweight F/J Framework were a blue-ribbon application
>> server. Regrettably, the framework is not a professional application
>> server."
>>
>> Nuff said ...
>
>
> So, are you saying that it IS an application server? Or are you saying that
> it shouldn't be considered an application server?

Of course it isn't and shouldn't be. It's a completely ridiculous statement.

> I too thought it was a weird statement to make when I read the piece, but
> isn't there a valid point in there somewhere?

If there is I couldn't find it.

Cheers,

Miles

Re: A Java Fork-Join Calamity

Added by Maxime Lévesque on 2012-02-11, 11:11


"If only the lightweight F/J Framework were a blue-ribbon application
server. Regrettably, the framework is not a professional application
server."


LOL !!!!

Copyright © 2013 École Polytechnique Fédérale de Lausanne (EPFL), Lausanne, Switzerland