Mikhail Fursov wrote: > In my opinion this is a very good idea to have public performance profile > with a hotspots identified. > So, if this idea is accepted by community we can start a discussion which > kind of profile might be useful.
I didn't think it was even a question :) > > I know that execution manager and optimizing JIT in DRLVM have a command > line keys to dump a lot of useful profiling information. I hope that other > components have such switches too. So the only thing we need to do first > (if > the your proposal is accepted) is to write a tool to parses this data and > shows as webpage. I can help to anyone with this task (importing profile > from DRLVM JIT/EM) or just find a time and do it by myself if no volunteers > will be found.. Why don't you kick it off by adding a page to the website on how to do this? At least how to get the info out... geir > > On 8/2/06, Stefano Mazzocchi <[EMAIL PROTECTED]> wrote: >> >> one thing that happened in mozilla-land that catalized the community in >> fixing leaks and performance issues was adding profiling information to >> the tests and start plotting them overtime. >> >> Not only that gives an idea of the evolution of the program performance >> overtime, but it also keeps people honest because profiling is not >> something that should be done once and being forgotten but something >> that should be considered part of the feature of the program. >> >> -- >> Stefano. >> >> > --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
