I can't help noticing that step 13, wich is like 'the other half' of the project has no real planning yet.
It is possible ofcourse to run this step (like most others that are finalized at the end) concurrent with the others.
To get this done, we first need to determine the performance and stability issues (what causes problems, in what situation?).
We can do that based on user input or on using profilers, monitoring, or other aides. We also need to determine if the same problems occur on diferent platforms.
We next need to analyze the cause(s) and determine if and how we will find a solution.
The main problem here is that user input is in general not very accurate or detailed. Most of the time, when things have gone wrong, by the time the problem is reported, what causued it has passed and is often untraceable.
We need to make a list of performance issues that are known, and these will then get focus in this Step. The bugtracker could be a good place to do this - it has a 'Performance' area where these bugs can be checked in.
Wel may also desire to seek for ways to monitor running MMBase code, or to seek the code for bad coding samples. Suggestions are welocme.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
