Gregg Wonderly wrote:
...
Can you help me understand why multiple builds are not working? It just
seems to me that you'd build the existing code "once" to test, and then
iterate through your development practices to work on your "Experiment",
testing with that output as you go.
...
Performance work is a bit different from functional development.
If two proposed implementations differ in functional correctness or
source code readability, the one that is better now is going to stay
better unless someone is working on the other one.
On the other hand, which of two implementation has the better
performance can change any time we move to a new JVM version, and new
versions of associated libraries.
One of the consequences of moving to JDK 1.5 is that I expect more and
more performance critical parallel code to be written in terms of
java.util packages. That means that code that is rejected for
integration because it is slower than another version may become better
than the integrated version without being under development.
I'm looking for a shelf I can put such things on where they will not get
lost. I would like to retain the ability to do performance run-offs
without having to maintain different versions of all code that depends
on the choice.
Ideally, it will be part of the River svn structure so that another
evidence-driver performance person can pick it up even if I'm no longer
active on the project, and also so that people with access to different
environments can repeat experiments.
Patricia
