Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (nike.apache.org: domain of stepan.mishura@gmail.com
 designates 72.14.204.238 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=u+6XxChHjwn3Lbgr/SrCPFGBh3Vg6PCku5ZfJOH/euHc1O8VpKzhanlGENULDr4YoZRZu2OfrikKsraftJboZn3LXfZZVCu3uWiZqAh64kRLlS/7QwhihQwAgWrDzMk/X9L2WV+BWkqrfLApVvyuCpSIveCYch0DVrOkUayb+RE=
Message-ID: <6e47b64f0804180204t7e28b35euea3e38ff3dd38d6d@mail.gmail.com>
Date: Fri, 18 Apr 2008 16:04:07 +0700
From: "Stepan Mishura" <stepan.mishura@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [general][repos] Benchmark repository
In-Reply-To: <4bebff790804172354n340a79d1g28f5bca11471aae3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4bebff790804150625v76a01165pc2c06cc5226cfcac@mail.gmail.com>
	 <211709bc0804152014j6dd7d8damef7407522a4fea4@mail.gmail.com>
	 <f944d83d0804152137j4a1e2b29y789216ee53f0d826@mail.gmail.com>
	 <6e47b64f0804152203u237b78c9xe5e423d6eda94324@mail.gmail.com>
	 <f944d83d0804152232m1238c82ap3f41f5ec7ab8f697@mail.gmail.com>
	 <6e47b64f0804152357h6b7a4baenb283fd3d130a8fbf@mail.gmail.com>
	 <94d710af0804160909m2f3f9577uccd7f1d27b45214b@mail.gmail.com>
	 <4bebff790804172354n340a79d1g28f5bca11471aae3@mail.gmail.com>

On 4/18/08, Aleksey Shipilev <aleksey.shipilev@gmail.com> wrote:
> So, should I make the benchmark ready for running via BTI?
> Are there any guidelines and criteria it should meet?
>

You should develop ANT build script that setup and run it. That is
enough to integrate it to BTI.

-Stepan.


> Thanks,
> Aleksey.
>
> On Wed, Apr 16, 2008 at 8:09 PM, Sean Qiu <sean.xx.qiu@gmail.com> wrote:
> > What about adding a web UI for our BTI?
> >  I think it is natural since we have a similar one to publish our results.
> >
> >  Just like continuum[1], it is easier to manage.
> >  Maybe we can get some hint from it.
> >
> >  Anyway, BTI is worthwhile devation.
> >
> >  [1] http://continuum.apache.org/
> >
> >
> >
> >  2008/4/16, Stepan Mishura <stepan.mishura@gmail.com>:
> >  > On 4/16/08, Alexey Varlamov <alexey.v.varlamov@gmail.com> wrote:
> >  > > 2008/4/16, Stepan Mishura <stepan.mishura@gmail.com>:
> >  > > > On 4/16/08, Alexey Varlamov <alexey.v.varlamov@gmail.com> wrote:
> >  > > > > 2008/4/16, Tony Wu <wuyuehao@gmail.com>:
> >  > > > > > Is it possible to integrate into BTI? if not we can consider the enhanced/tools/
> >  > > > >
> >  > > > > There is one already in drlvm trunk, see working_vm/src/test/microbenchmark.
> >  > > > > There is no infrastructure around, it is mere store holder for now.
> >  > > > > Feel free to add benches there, they are not intended to be
> >  > > > > VM-specific.
> >  > > > >
> >  > > >
> >  > > > I would say opposite if they are DRLVM specific then it is OK to put
> >  > > > them to the folder. Otherwise (i.e. they are not VM-specific) we
> >  > > > should integrate them to BTI.
> >  > > >
> >  > > > Th point is that DRLVM workspace should contain only DRLVM specific
> >  > > > tests. For example, IMO DRLVM workspace is not the right place for
> >  > > > EHWA-API scenario.
> >  > >
> >  > > This is too radical position IMO. Absolute majority of tests in DRLVM
> >  > > are functional and not impl-specific, should we move them all to BTI?
> >  > >
> >  >
> >  > Yes, IMHO we should move them to BTI.
> >  >
> >  > The point is that any workspace (classlib/drlvm/jdktools) is not a
> >  > repository for a set of different suites.
> >  >
> >  > > Sometimes convenience of using and extending is more important for
> >  > > success. If we had appropriate infra for benchmarks I wouldn't argue,
> >  > > but now I'm afraid most contributors would rather leave a bench-case
> >  > > hanging in JIRA than dare to hack BTI. I'm happy to be proven wrong,
> >  > > though.
> >  > >
> >  >
> >  > "convenience of using and extending" is questionable for me in this case.
> >  > Well, yes I agree that from position of a DRLVM developer it is more
> >  > convenient when EHWA-API scenario is located in DRLVM workspace - no
> >  > additional efforts are required to run it. But what about classlib
> >  > developer who wants to run EHWA-API on J9 - she/he needs to checkout
> >  > DRLVM workspace. Is this convenient and extensible? (Hmm, may be I was
> >  > wrong when I insisted on integration of LDAP scenario into BTI then
> >  > into classlibrary ;-))
> >  >
> >  > Seriously, if we think that using BTI is complicated for a developer
> >  > then we should do our best and make it simpler and more convenient.
> >  > Otherwise we finish with zoo of different suites/scenarios in several
> >  > places.
> >  >
> >  > Thanks,
> >  > Stepan.
> >  >
> >  > > Regards,
> >  > > Alexey
> >  > > >
> >  > > > Thanks,
> >  > > > Stepan.
> >  > > >
> >  > > > > Re integration to BTI, this would require fair amount of efforts and
> >  > > > > usage model is not clear to me.
> >  > > > >
> >  > > > > >
> >  > > > > > On 4/15/08, Aleksey Shipilev <aleksey.shipilev@gmail.com> wrote:
> >  > > > > > > Hi Tony, all!
> >  > > > > > >
> >  > > > > > > Does it make sense to create special place in our repository for
> >  > > > > > > storing the benchmarks like this one I've used in my performance
> >  > > > > > > researches on Harmony? It would be great to have them synchronized in
> >  > > > > > > repos rather than store in JIRA.
> >  > > > > > >
> >  > > > > > > Thanks,
> >  > > > > > > Aleksey.
> >  > > > > > >
> >  > > > > > > On Tue, Apr 15, 2008 at 11:00 AM, Tony Wu <wuyuehao@gmail.com> wrote:
> >  > > > > > > > Aleksey,
> >  > > > > > > >  I think keep the benchmark somewhere such as JIRA is also ok.
> >  > > > > > >
> >  > > > > >
> >  > > > > >
> >  > > > > > --
> >  > > > > > Tony Wu
> >  > > > > > China Software Development Lab, IBM
> >  > > > > >
> >  > > > >
> >  > > >
> >  > >
> >  >
> >
> >
> >  --
> >  Best Regards
> >  Sean, Xiao Xia Qiu
> >
> >
> >
> >  China Software Development Lab, IBM
> >
>