Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of vdichev@gmail.com designates
 209.85.219.220 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        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;
        b=F6FzYpdWMYqgIHdCUNtnYkxLRO3onmg8syJFcdXubFaofvIn3JGLPpWagfxHjp+kG7
         dIZCy+EXH0r4CfyQQa9e6H9AjxCPWceyYXZRMJ/r6ToKxAEb/wGW1SSVll36Yt5mLd8r
         uJoyBaqk/NER0bhAlQleMpi8V9g0S0bF9351A=
MIME-Version: 1.0
Sender: vdichev@gmail.com
In-Reply-To: <06802A3D4BE62D449D366CE4A27D614003011676@usphle16.phl.sap.corp>
References: <06802A3D4BE62D449D366CE4A27D614003011676@usphle16.phl.sap.corp>
Date: Thu, 26 Nov 2009 09:15:02 +0200
Message-ID: <c7fc82820911252315i1cfde06bq3c1a231c0f14d417@mail.gmail.com>
Subject: Re: Further analysis of the GC issue
From: Vassil Dichev <vdichev@apache.org>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Facebook are definitely not relying on the database, they virtually
have everything in cache. You can't scale/distribute an RDBMS the way
they are growing- more than half a million new users every day. And
it's not only them.

If there are problems, they are not with Scala, as some of the
highest-traffic sites use it, for instance Twitter. It's more likely
that it's a problem of ESME or maybe Lift, as we are using the
SNAPSHOT branch and they had many changes lately. But I definitely
remember that ESME was faster one or two months ago.

Maybe we also have to try to profile the stack trace where the biggest
number of String objects get allocated. It might be slow, but will
certainly clarify many questions. The important thing to do it is that
we are easily able to reproduce it, so selenium/load tests would be
cool.