Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 390967D7A for ; Sat, 22 Oct 2011 10:17:49 +0000 (UTC) Received: (qmail 28756 invoked by uid 500); 22 Oct 2011 10:17:48 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 28681 invoked by uid 500); 22 Oct 2011 10:17:48 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 28673 invoked by uid 99); 22 Oct 2011 10:17:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Oct 2011 10:17:48 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of simone.tripodi@gmail.com designates 209.85.160.171 as permitted sender) Received: from [209.85.160.171] (HELO mail-gy0-f171.google.com) (209.85.160.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Oct 2011 10:17:43 +0000 Received: by gyg13 with SMTP id 13so6575779gyg.30 for ; Sat, 22 Oct 2011 03:17:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=jvgNQNwRmplwFig4UUZGIA6AqxjNT8aFn54tfK8HSwo=; b=AkZBOkBlfyaEMQBlc8vcFs6JBx9onVM8whggTKO2BCFsHPyajDcIM2G5g3jgxvdRMJ OvInRn+d112iWTkIIgRiU0a1NfQ+DXvjiclr8hKJrwbjMnYq0f1vqzBbfQQrbsRaRh5p Nqa/EOkf/Bi7L6DF2Rs8VrWDxcuxSX145a9I8= MIME-Version: 1.0 Received: by 10.151.9.17 with SMTP id m17mr15804054ybi.101.1319278642104; Sat, 22 Oct 2011 03:17:22 -0700 (PDT) Sender: simone.tripodi@gmail.com Received: by 10.150.96.13 with HTTP; Sat, 22 Oct 2011 03:17:22 -0700 (PDT) In-Reply-To: References: Date: Sat, 22 Oct 2011 12:17:22 +0200 X-Google-Sender-Auth: MPhT6A_C871MVK96WEBIvDXIcZc Message-ID: Subject: Re: [OGNL] Performance analysis From: Simone Tripodi To: Commons Developers List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Mau, that for the explanation, that really helps on clarifying the graph!!! I have an idea about merging the tests in trunk with a profile approach that I already submitted for the Disruptor project[1] - they have performance/benchmark tests too - if it is fine for you I can work on it - not today that's Rugby day, maybe tomorrow :) All the best and have a nice WE, Simo [1] http://code.google.com/p/disruptor/issues/detail?id=3D2 http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sat, Oct 22, 2011 at 10:00 AM, Maurizio Cucchiara wrote: > I almost forgot there are even old vs commons comparison. Stay tuned :) > > Twitter =C2=A0 =C2=A0 :http://www.twitter.com/m_cucchiara > G+ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:https://plus.google.com/10790371154= 0963855921 > Linkedin =C2=A0 =C2=A0:http://www.linkedin.com/in/mauriziocucchiara > > Maurizio Cucchiara > > > > On 22 October 2011 09:58, Maurizio Cucchiara wrot= e: >> Thank you Simo, >> Ok, I realized after that the graph needs at least a short explanation: >> In that test I have tried to test every caches which I re-engineered. >> In the graph you mentioned, there are depicted 3 different kind of >> cache implementations: >> 1. Concurrent HashMap (CHM) >> 2. Thread-safe HashMap (HM) >> 3. Reentrant Read Write Lock (RRWL) >> >> As you will notice, there are some cases where RRWL is faster, other >> where CHM and so on. >> So there is no yet a real winner approach, though, at very quick look, >> CHM seems to be the slower one (my guess is that it's the only >> not-fully thread safe). >> >> To answer your question about projects merging, they surely could work >> under the same project, my only concern is about the execution time. >> At the moment I'm writing the whole execution time is near 50 seconds >> (currently the non-benchmark side take more or less 20 seconds). >> Furthermore the benchmark tests don't give you an answer in term of >> correctness (aside from the concurrency issues), =C2=A0ATM the only >> motivation behind them is performance measurement. >> Next time I could check the hit/miss ratio. >> Twitter =C2=A0 =C2=A0 :http://www.twitter.com/m_cucchiara >> G+ =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:https://plus.google.com/1079037115= 40963855921 >> Linkedin =C2=A0 =C2=A0:http://www.linkedin.com/in/mauriziocucchiara >> >> Maurizio Cucchiara >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org