Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (nike.apache.org: domain of ronchalant@gmail.com designates
 209.85.223.196 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=jo8G/8BBN3mhGoyQ6ZlqSEb6E/08dIk13Tl1xdMi3j6TBvIUPkmEbhsdSpe5CgK8bl
         2VtqaRmZwZoB5t1cWh1iDoezTaZ3ErlmXVt1SkzFK5O2FLt2sV/jB+HJrWczfeE8CuQf
         w8Tok5n2z/aXEEH+4sEBuUltKDwcyRLXZjJ84=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: Derby 10.3 Performance
From: Ronald Rudy <ronchalant@gmail.com>
In-Reply-To: <o2k679f019c1004090139w4f8ea9a9xc51f376f3fe117e6@mail.gmail.com>
Date: Fri, 9 Apr 2010 09:43:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8559000A-9E25-4FB4-B98C-00955870F075@gmail.com>
References: <o2k679f019c1004090139w4f8ea9a9xc51f376f3fe117e6@mail.gmail.com>
To: "Derby Discussion" <derby-user@db.apache.org>

I don't know specifically with regards to Derby, but typically this is =
more of a function of how you configured your JVM and how you utilize =
Derby itself.  If you have many threads doing work, leveraging =
asynchronous processing where you can, then you'll be utilizing the CPU =
as much as possible.  I've found in practice that a bigger determinate =
for performance with Derby is your disk speed.

-Ron

On Apr 9, 2010, at 4:39:35 AM, Rajesh Datla wrote:

> Hi All,
>             I like to know the performance utilization of  =
multi-processors on a machine by Derby 10.3. Does Derby 10.3 utilize all =
CPU's on 8 CPU machine?.
>=20
> Regards
> Raj