Home » Modeling » EMF » [Validation] Deterioration of performance with Eclipse Galileo due to Tracing
| | | |
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 Messages: 14 Registered: July 2009 |
Junior Member |
|
|
Hm,
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.
Cheers,
Boris
"Eike Stepper" <stepper@esc-net.de> wrote in message
news:h46mss$69n$3@build.eclipse.org...
> Guys,
>
> You might be interested it this bugzilla I filed 3 years ago:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=162347
>
> Please consider voting for it! ;-)
>
> Cheers
> /Eike
>
> ----
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>
> 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,
>> Boris
|
|
| | |
Goto Forum:
Current Time: Mon Jun 17 05:30:49 GMT 2024
Powered by FUDForum. Page generated in 0.03445 seconds
|