[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-releng-dev] Performance re-testing on releases and 3.1 milestones
|
Sonia,
- what's the reason to use elapsed time for all assertions and
fingerprints? There might be tests that want to use CPU. Is this no longer
allowed?
- most of the CPU assertions come from the performance test framework's
default and it has to be changed there
- as Wassim already mentioned, some 3.1 M[1-5] tests will not compile
against perf_30
Dani
platform-releng-dev-bounces@xxxxxxxxxxx wrote on 12.04.2005 23:17:38:
>
> Starting this Friday, we would like to run performance tests on
> previous releases (starting at 2.1.3) and 3.1 milestones to generate
> a new history of performance measurements on four newly configured
> performance test machines. These will consist of two identical
> "slower" machines (Intel P4 2 GHz, 512 MB RAM) and two identical
> "fast" machines (Intel P4 3 GHz, 2 gig RAM) which will run Windows
> XP (SP1) and Red Hat Enterprise Linux WS 3. This task will require
> approximately 80 hours to complete and if all goes smoothly, we
> expect to have all the re-testing done by Wednesday April 20.
>
> Please see http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%
> 7E/platform-releng-home/performance_test_plan.htm for further
> details and background.
>
> In order for us to proceed, we ask ALL teams using CPU Time in
> assertions and summaries (ie. fingerprints) to switch to using
> Elapsed Process in HEAD and perf_* streams of your tests where needed by
> 11pm (Ottawa time) Thursday, April 14.
>
> Please respond to this list with questions or comments.
>
> Sonia _______________________________________________
> platform-releng-dev mailing list
> platform-releng-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
