disabling the "transaction indicator" helps a little but is not the solution on my site

I too had slow response when running the beta version. I have not ried the latest release because of that problem and the fact that it is still being reported.

Hello,
It seems to me this issue is strongly underestimated, for our company to buy new 20 licences is unacceptable, if we should get product with worse performance than previous version. All new features should be fine, but the performance is the core.

Please notice me (us) when this issue will be solved.
Thank You,
David.

For people having performance problems, can you try the following with version 11.0.1 (released yesterday):

• Exit PL/SQL Developer
• Go to the PL/SQL Developer installation directory
• Open the Params.ini file
• Add the following line:
  OldLocking=1
• Save the file
• Restart PL/SQL Developer and verify if this affects the performance issue

Thank you Marco. This new version does finally feel a lot better again and v11 seems to finally be usable.

I want to thank you too Marco. This version looks fine, speed is normal again, so we may finally start to use 11 instead of 10

Pavel

Did you use the OldLocking=1 line in Params.ini?

I can report success too. I didn't change the params.ini. The speed when jumping to another window feels even faster than in version 10 for many (20) windows open!

Thank you,
Timo

Sorry, I have to take back the initial impression I had yesterday. Today it's back to the same old awful response time, forcing me again to go back to v10. Yes, I was using the OldLocking=1 line in Params.ini.

Looks like this parameter actually made it all worse. Without the parameter performance was acceptable for a while, but then has become unbearable again.
I've had enough again: Going back to v10!

Is it fast again when you exit and restart version 11?