I don't know what kinds of changes folks have planned for the current Flex SDK code, but other than the CSS perf fix, I haven't seen too many other things that would make getting this stuff through an audit a priority.
The problem with any perf suite that runs on people's computers is the possibility of variances between runs that are unrelated to the code changes. I think we had a dedicated sandboxed computer for official testing at Adobe. On 12/10/12 7:04 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: > And I didn't say that was for Apache but more for committers, when someone > tells you what he did breaks performences, I want to be able to demostrated > too > > -----Message d'origine----- > From: Frédéric THOMAS > Sent: Tuesday, December 11, 2012 3:46 AM > To: flex-dev@incubator.apache.org > Subject: Re: CONFIG::performanceInstrumentation / PerfUtil? > > PerfSubmitter probably talks to an Adobe thing and I'm pretty sure that's > private too but I'd like to be able to develop the same class without doing > a war with Adobe's legals, that's my point. > > -----Message d'origine----- > From: Alex Harui > Sent: Monday, December 10, 2012 8:07 PM > To: flex-dev@incubator.apache.org > Subject: Re: CONFIG::performanceInstrumentation / PerfUtil? > > > > > On 12/10/12 10:00 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: > >>> I think it was a plug-in that fed results to a reporting infrastructure. >> I'm not so sure we need it but we could try to get it donated. >> >> I comeback on that because it would be nice to be able to test the perfs >> on >> parts of the framework but I noticed that not all the framework/tests >> directory has been donated and notably, the performance one. >> >> Will it be donated ? > We can look into it, but I'm not sure it is worth the effort. I think it > plugged into a server-based reporting infrastructure that we have no way to > replicate in Apache, and it certainly didn't catch some of the issues that > folks are trying to fix now, plus performance on individual machines varies > widely. > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui