Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dan.creswell@gmail.com
 designates 209.85.216.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=sjc1yxGfTh+0qtXkVf0ofwGy4+wrAkl7NCqcaEN0+mby+2u7+JquRa8rvbRRUbBgMd
         EHxC2KYIiq+q7wdvK6kz4NSXTz9Ho+waYoQrKjHmn3jQe6Bi5406tlXAjK+6LY/7B+QI
         MUHc7A6Gv8YiD4JmGGorBfm2XpRdmzoRq8K38=
MIME-Version: 1.0
In-Reply-To: <4D0FBCCD.8080506@acm.org>
References: <4CF89BD3.3030103@acm.org>
	<4CF909A0.5070409@wonderly.org>
	<4D056E41.7020102@acm.org>
	<4D057B73.3090905@zeus.net.au>
	<4D05BA22.4000002@acm.org>
	<4D06672A.10203@wonderly.org>
	<4D066FA2.8050207@wonderly.org>
	<4D069D21.5070908@zeus.net.au>
	<4D06BA8D.4040602@simulexinc.com>
	<4D06C523.5000006@acm.org>
	<5E44AB11-EC78-476E-8A6D-C9AEBEFCA3D2@topiatechnology.com>
	<4D079D60.4070607@wonderly.org>
	<4D07E442.5040908@acm.org>
	<39AED645-40CC-4314-9956-25BE1325B2F5@topiatechnology.com>
	<4D07E9D4.2080106@acm.org>
	<B9558304-8B77-4CFB-B23B-73A29D89B65F@topiatechnology.com>
	<4D0856B2.1070107@acm.org>
	<DD8D109E-0158-438A-ADB0-F8180C8B01A8@topiatechnology.com>
	<4D0A1A61.2020805@acm.org>
	<4D0A1D90.2000900@qcg.nl>
	<4D0B8903.8090704@wonderly.org>
	<4D0BFA6D.80201@acm.org>
	<AANLkTimzaLEMmb6iRPPWAsVgRyc8bvyfrGTHzt9NnPUw@mail.gmail.com>
	<4D0FBCCD.8080506@acm.org>
Date: Mon, 20 Dec 2010 21:13:01 +0000
Message-ID: <AANLkTikkSw6+XMe7GLU0X6EqZsFoA9WG3qTO-grswp5V@mail.gmail.com>
Subject: Re: datastructure classes
From: Dan Creswell <dan.creswell@gmail.com>
To: river-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0015175ca8764e9dc50497ddfc73

--0015175ca8764e9dc50497ddfc73
Content-Type: text/plain; charset=ISO-8859-1

Blitz too has optional FIFO-ness via configuration though it's absolutely a
performance killer for any decent concurrent load by virtue of the usual
suspects such as lock contention and the high chance of scanning entry's
that have just been taken by a thread just ahead in the queue.

To be honest though, unless FIFO is spec'd officially as an option or a
default, having developers rely on magic such as FIFO by default is "very
bad" (TM).

On 20 December 2010 20:30, Patricia Shanahan <pats@acm.org> wrote:

> Tom Hobbs wrote:
>
>> I know of at least one company which uses Outrigger specifically
>> because of it's fortuitous FIFO behaviour.  I'm trying to encourage
>> them to move from the Jini 2.1 code to the River release and losing
>> the FIFO-ness might be an issue for them.
>>
>> And yes I know, the spec doesn't specify FIFO, like I said, they
>> needed a FIFO space, and Outrigger "just happened" to behave like
>> that.
>>
>
> That confirms my suspicion that FIFO-ness is a useful property. I note that
> Gigaspaces has optional support for FIFO.
>
> My quick changes to try to fix the current bug will preserve it. If the
> long term design loses it for flat-out performance, we should make it
> available on a configuration basis.
>
> Patricia
>
>
>

--0015175ca8764e9dc50497ddfc73--