|Re: [Validation] Deterioration of performance with Eclipse Galileo due to Tracing [message #431703 is a reply to message #431700]
||Wed, 22 July 2009 10:51
| Boris Gruschko
Registered: July 2009
3 years ago wasn't 3.5M6 and the calls didn't take that long.
I'll open a bug for platform and relate it to 162347.
"Eike Stepper" <email@example.com> wrote in message
> You might be interested it this bugzilla I filed 3 years ago:
> Please consider voting for it! ;-)
> Boris Gruschko schrieb:
>> Hi Mario,
>> thanks for the detailed bug report.
>> It would probably be the most simple thing, to just cache the
>> isDebugging value. However the problem is not the caching itself, but
>> keeping cache's value coherent with the reality.
>> As the debugging/tracing option is relevant to the developers only,
>> I'd be tempted to insert this cache first and then wait for the
>> platform to fix the underlying issue.
>> Could you please open a bug on the validation component, I'll try to
>> provide a fix today afternoon and schedule followups with platform.
>> Thanks again for the detailed and helpful analysis,
Powered by FUDForum
. Page generated in 0.01834 seconds