Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of beneritter@googlemail.com
 designates 209.85.210.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F5D0951.2080306@apache.org>
References: <4F5CB10C.507@apache.org>
	<CAB917RKE19fn=2N63zMivvFL_4vLLDmBfxgM54E3Xq-2OOV_Bw@mail.gmail.com>
	<4F5D0951.2080306@apache.org>
Date: Mon, 12 Mar 2012 00:02:08 +0100
Message-ID: 
 <CAB917RJtPyoCOtOTKQdpjs699zf9eMA7LD2D42Q_0zXMCNXgnA@mail.gmail.com>
Subject: Re: [csv] Performance comparison
From: Benedikt Ritter <beneritter@googlemail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Am 11. M=E4rz 2012 21:21 schrieb Emmanuel Bourg <ebourg@apache.org>:
> Le 11/03/2012 16:53, Benedikt Ritter a =E9crit :
>
>
>> I have some spare time to help you with this. I'll check out the
>> latest source tonight. Any suggestion where to start?
>
>
> Hi Benedikt, thank you for helping. You can start looking at the source o=
f
> CSVParser if anything catch your eyes, and then run a profiler to try and
> identify the performance critical parts that could be improved.
>

Hi Emmanuel,

I've started to dig my way through the source. I've not done too much
performance measuring in my career yet. I would use VisualVM for
profiling, if you don't know anything better.
And how about some performance junit tests? They may not be as
accurate as a profiler, but they can give you a feeling, whether you
are on the right way.

Benedikt

> Emmanuel Bourg
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org