|
[openbeos]
||
[Date Prev]
[02-2003 Date Index]
[Date Next]
||
[Thread Prev]
[02-2003 Thread Index]
[Thread Next]
[openbeos] testing enhancement
- From: Kobi Lurie <k_lurie@xxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Thu, 20 Feb 2003 17:05:04 +0200
Hi,
right now, after the build finishes, since the OS isn't ready to be used by
itself, most testing is done using the unittester..
when it comes to performance comparing we have the time it took.
but this doesn't really show us if it's faster/slower than the equivalent R5
implementation, or from recent implementations of the code.
thus, i suggest the "score" would be kept somehow.
a possible implementation would be a directory called speed
it would have R5.txt obos[date].txt and obos[now-date].txt
then, when the unit tester measures the performance it can also
show if we're faster/slower.
since it's command line, we can also dedicate a machine to doing a test every X
minutes and notify if there has been a slowdown.
so the one in charge would be notified and think of an optimization.
|
|
