Re:MultiQueues: Simpler, Faster, and Better Relaxed Concurre...
by thrownaway2424 on Sunday November 09, 2014 @11:59AM
(#8580242)
The SprayList paper is quite a bit more detailed, and it's underhanded how the MultiQueues paper shoves the bad news into an addendum, but the interesting thing to me is these papers coming out within weeks of each other.
Re:MultiQueues: Simpler, Faster, and Better Relaxed Concurre...
by throwaway1567 on Sunday November 09, 2014 @01:48PM
(#8580502)
Unfortunately Microsoft patents at least some of the MSR research on algorithms and data structures, which makes it effectively unusable for many users.
Re:MultiQueues: Simpler, Faster, and Better Relaxed Concurre...
by kethinov on Sunday November 09, 2014 @02:06PM
(#8580544)
This kinda reminds me of the opening scenes of Silicon Valley.
Just imagine someone getting up on stage and yelling enthusiastically, "Simpler, faster, and better relaxed concurrent priority queues!" To a round of muted applause.
I'm sure this submission has tons of technical merit and all that. But without context, that scene from Silicon Valley is all I can really think of. :)
Re:MultiQueues: Simpler, Faster, and Better Relaxed Concurre...
by vegedor on Sunday November 09, 2014 @07:44PM
(#8581468)
Probably, the whole paper is written in that terse tone. If the title doesn't appeal to the reader, reading on wouldn't make sense anyway. I.e., I can tell from the title that I'd be better of returning to the other book on data structures.
Just imagine someone getting up on stage and yelling enthusiastically, "Simpler, faster, and better relaxed concurrent priority queues!" To a round of muted applause.
I'm sure this submission has tons of technical merit and all that. But without context, that scene from Silicon Valley is all I can really think of. :)
I know we're a technical audience, but I'd be willing to wager more than half of this site's audience has no clue what that title is talking about.
Prefixing it with something like "A faster algorithm for [purpose]" is helpful. Otherwise it can just sound like technobabble.
I don't think it's inane to point out that jargon sounds jargony to those not in the know.
I'll download it for later(tm).
If you weren't expecting to find detailed technical articles, you might be on the wrong website.