Hello,
Im reposting this topic from beta-forum, which seems to be closed.

Environment of version 11 is noticeably slower than previous version 10. It's hard to define all (slower) actions, I can describe one very simple operation. Steps are:
- start PLSQL Developer (without any connection)
- open 10 new "SQL windows"
- connect to (any) database (it makes all 10 windows connect to database)
- and now: just close all 10 windows as quickly as possible

I joined an attachment of screen captures - ver10 and ver11. This simple actiona takes me about 15sec in ver10, but 30sec in ver 11.

This is just example (I dont' enjoy closing ten windows every ten minutes) but there're a lot of actions slower than ver10 which is annoying, so I have to stay with 10 for now.

plsql10 screencapture

plsql 11 screencapture

Thanks for response.
David

We're looking into this.

I find this behaviour really annoying too. Version 11 spends it life a lot more in sand clock-mode for no obvious reason. Just switching between the windows of my project already takes lots of time. There's also the really irritating effect that you click somewhere and for several seconds nothing seems to happen at all. Another effect is that with some of such long time taking actions in task-manager the instance seems to split for a while and then re-unites before becoming usable again. I'm currently thinking about using version 10 for now again, as version 11 doesn't seem to really be mature enough yet to be used productively.

I have done some further research. I have a project with 33 windows.

1. Opening this project takes
about 1 min 50 sec in v11 compared to 1 min 40 sec in v10.
=> About 3 sec per window is not acceptable and should have been faster in both v11 and v10.

2. Clicking through all my 33 project windows takes
about 2 min 10 sec in v11 compared to 1 min 00 sec in v10.
=> That is not acceptable in v11 while it was just about ok still in v10.

3. Closing this project takes
about 20 sec in v11 compared to just 3 sec in v10.
=> Not acceptable in v11, was fine in v10.

The reason why I keep quite a lot of windows open in my projects is that they often use a lot of different connections and without keeping the windows open I would loose the info, which project item should be opened with which connection. I would much rather prefer to have that info stored in the project items themselves already and have them remembered when reopening project items.

Can you try if the following affects performance?

1. Go to Tools > Preferences > User Interface / Options and disable the "Show transaction indicator in Window List" option
2. Close the Window List
3. Go to Tools > Preferences > User Interface / Editor and disable the "Highlight parentheses" option

Let me know if any of these steps affect performance.

Here my results (all options have just been tested individually):

A) With "Show transaction indicator in Window List" option enabled:
Opening Project : 1 min 10 sec => even better than v10!
Click trough all 33 windows: 1 min 00 sec => same as v10!
Close Project : 0 min 03 sec => same as v10!

B) With closed "Window List"
Opening Project : 1 min 25 sec => still a little better than v10, but not as good as v11 in A)
Click trough all 33 windows: not really possible the same way then
Close Project : 0 min 20 sec => as bad as before

C) With "Highlight parentheses" option disabled
Opening Project : 1 min 25 sec => still a little better than v10, but not as good as v11 in A)
Click trough all 33 windows: 1 min 15 sec => a bit worse than in v10 still
Close Project : 0 min 20 sec => as bad as before

So looks like the really bad guy is the option "Show transaction indicator in Window List".
With this one disabled as in A) we were back to as good or even better than v10 - in my tests at least.
It's not really a new feature, is it?
I mean PSD did that in v10 already. The feature could just not be disabled in settings then.

During all the tests I did it's not really possible to have any transaction happening. That can only be the case once you execute anything. So couldn't you eliminate transaction testing there or at least make it a lot faster so it won't bother anybody?

The transaction indicator in new in 11.0. We'll check it out.

Hi Marco. Just for info - I have same problem, new version is really slow, after Ive uncheck Show transaction indicator in Window List and Highlight parentheses its become slightly better, but there is still problem.
When Ill click on opened window in window list on right side where SQL/Output/Statistic window is I see window I expected, but it takes 3 seconds before on window list is highlighted that actuall window. No matter what kind of window - sql or command window is it.
Hope that this will hepl you to resolve this problem. Ive installed 11 today, so I have most actuall version..

Pavel

And I hope that you have this as priority one bug, because using plsqldeveloper with it is really pain. Ive tried to give these highlight and show transaction parameters back, copied some commands into cmd window and whole develper frozen for few minutes till last of the commands executes. In 10 I was able to copy commands into cmd window, switch to another and work normally till cmd commands ends..

Pavel

I hope as well this is considered as a priority one bug. Even when switching off those preferences PSD v11 is really slow. I have the feeling when more instances are open that slowing it down even more too. A lot of things seem to work in slow motion really. It feels like we're running in debug mode all the time.

We're looking into this.

Is there any progress with this issue?
thank you.

An additional hint may be that when starting V11 (without any connection to a database) the internal initialization takes longer then in V10.

Extremely slow v11 response is forcing me again to switch back to v10. When reorganizing a project v11 is really unbearable!

Every window change inside PLD including the change from search dialog to editor window lasts about 5 seconds.

I also have to go back to version 10.

Is there any progress in the development?

Not yet, we're looking into this.

Marco, could this problem at least be confirmed by development?
Do you need any more info from affected users?
I'm also wondering how many users are actually affected.
Could we get some more feedback from both sides, please?

We have not yet been able to reproduce such performance problems. But as stated above, we are looking into this.

We too have the same slow response issues with version 11. Switching back to 10.5. Do let us know if and when this gets addressed.

I am also have the same problem with slowness. It appears the disabling the "transaction indicator" definitely helps. A simple example that I confirmed is closing the "Find & Replace" window.

When the Transaction Indicator is enabled, it takes about 3 seconds for the Find & Replace window to close.

When the Transaction Indicator is disabled, it closes instantly w/o any lag.

Thanks,
Joe

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?

No, Ive just installed new version, without param change.

But there is one thing - I had plsqldeveloper opened all night and today switching was slower then yesterday. Not as bad as in 11.0.0 was, but slower then in 10. After closing plsqdeveloper and reopen it switching speed is quick again. And problem wasnt just only in switch between windows, but on switching in sql window between sql and outpout too.
I try to test it tomorrow, Ill let plsqldeveloper opened all night and then let inform you if this problem appears again.

Pavel

It's fast again after restart.
It seems to slow down faster and more tremendously too, when more PL-SQL-Developer-instances with lots of window-list-items are open.

So Ive done test again as I promise. Ill let it open whole night and today it was slow again. Click to next window takes around 3 seconds. After close and open again plsqldeveloper it goes back to normal speed. Hope this info helps with problem resolution.

Pavel

Can you try this preliminary version and let me know if this affects the issue?

I'd like to test performance in new version too but my trial period for 11 expired so I'm screwed

You can send an e-mail to support@allroundautomations.com to obtain a trial extension.

Ill try it today, so results you will have yesterday. Anyway I had plsqldeveloper open from Saturday, today response looks fine, till I clicked on connections. Unroll connection list from "hidden" window is slow and it looks like after that click between window list starts to be slow too. After close and reopen plsqldevelper connection window and window list is quick again. Not sure if there are any dependencies between connection and window list, but maybe this will help you to find why this happens.

Pavel

Another test - when Ill connect to my production DB, open one sql window with select, second window with connect to production DB switch between sql and output is fast. When Ill connect on second window to my test DB switching between sql and output become slow. Not so much but its visible. Closing window with testDB will not help. Ill try another test
open one livedb window, second livedb window. Do select on first window, switch between sql and output, speed was Ok - almost invisible speed.
Close second window, response of switching sql-outpout in first window starts to become slower. Its under 1s, but its visible.
Ill open second window, now Ill connect to testDB and switching between sql-output become more visible, it takes maybe 1s now..

Open connection window will take more than 1s (maybe 2s?).

On new version youve send me its almost the same, maybe open connection window is little quicker after last test.

I dont understand what dependencies are there, hope that
youll find them.

Pavel

Hi Marco
New version looks fine, it looks like its no slower then yesterday when it run all night, Ill try to let it go today night and we will see yesterday if it will be the same. But for first sight its quicker then old 11 version, which is today slower as we expected.
The problem with slower response (click to new window, switch between sql and output) when open window to test DB persist.

After few tests - new test version have the same problem as old one, after opening few new windows with new connections it become slower and slower. Im unable to work with it, because wait 3 seconds to switch between windows is really annoying. From my point of view this is bigger problem than that plsqldeveloper become little slower when run whole night. I may restart it on morning, but when it become slower everytime Ill open new window, this is something I cannot use for daily work.

Pavel

I can confirm Pavels problems. My first post about success after installing 11.0.1 was to early.
And no improvement with 1101.1765 ...

Sorry, no more time currently for testing this issue. Hard to come to any conclusions about it really anyway.

Another clue maybe - I have 5 windows open on the same database and speed is OK. When Ill open new window with new live database speed goes slightly down (its more about feeling than exact time). When Ill open new window then with test DB where connection takes little longer time speed of switching goes down to two seconds. Cannot this be clue? Isnt there any check or something which will ask all opened DB when Ill switch to another window? And because asking into test DB is slow it affect all other windows too?

Ive tried to close window with that new live and test DB and speed of switching goes up to normal. OK, still its little slower then Ill expected, but its below 1s again...

Pavel

Hi all,
I too am experiencing this slow response time. I have not yet used the new version for any development, but I have noticed substantially slower performance when attempting to open SQL files. When using version 10 and opening previously created SQL files, the file opens almost instantaneously. However, when opening the same files in version 11, it can take up to around half a minute to load. Troubleshooting, I've found that this is only true for those files that are stored on a network drive at my company. When loading the same files with version 11 from a local drive, they load close to instantaneously. I do not experience any slow down when loading from both local/network locations with version 10.

I have attempted all the suggestions so far, but nothing has changed this performance issue.

You get easily slow response times and see lots of sandclocks when comparing half a dozen schemas each with a few hundred objects. Just switching to the PL/SQL Develoepr application takes about 10 sec. Windows then even even detected unresponsiveness and suggested to kill the PL/SQL Developer instance. Some compares also seem to have hung up completely and don't seem to move forward anymore. Switching from one compare window to the next also already takes many seconds.

Today test - plsqldeveloper open from Friday till today is quicker than on last test which Ive done last week. This test was different from test on last week in which I had open sql windows for two databases. On actuall test I had open two plsqldevelopers, but every on 1 database connection only. So problem will be as I wrote last week only when windows are open for more then one database. Marco are you able to confirm this on your test too? Have you any date when you expected this will be repaired? Because as I wrote without that repair we still will use 10 instead of 11...

Pavel

We have not yet been able to reproduce the performance problem, but we are trying to optimize everything as much as possible.

What exactly is slow when you have 2 PL/SQL Developer instances connected to 2 different databases?

I would say pretty much everthing is slow then. Especially slow however is switching between different window list items and changing a connection.
Have you tried the scenario where I got the response time problem easily and compared about six schemas each with a few hundred objects? Do the same in v10 and v11 and you should see a very fundamental difference in response times.

I found that 3 things independently lead to the poor performance

- more than one db connection
- many windows inside one instance (how many?)
- leaving the instance open while using other applications for longer time and than come back

poor performance means
- when activating a window (doesn't matter if you were in an other application or only in an other PL/SQL Developer window) you have to wait up to 8 seconds before you can do anything.
- the same when going from search dialog to window
- after executing a statement you see how many rows will come because the rownumbers come fast, but the grid is filled seconds later

To Marco - Switching between sql windows, on sql window switch between sql and output window.

Pavel

To Marco - Ive tested actuall version of plsqldevelper 11.0.2.1766 to found when slow response appears and here is what Ive found.

Two Plsqldevelpers opened from last week (4 or 5 days of run), few work during weekend.

1 - developer which had open only one database connection all the time is quick even now after that 4 days of run. I have there around 5 windows opened all the time, switching between them is quick, switch between sql and outpout is quick too. 4 windows are plsql, 1 window is program window.

2 - developer which had open connection to three databases is slow. Switching between windows takes around 3s, the same is switch between sql and output. Developer is open 4 or 5 days too, Ive opened it in same time as developer 1.

So from this testcase you can see that problem will not be in time how long developer is open as we think after first tests, but with count of connections open to different databases.

Hope that this will help you to resolve this problem quicker.

Pavel

So PL/SQL Developer becomes slow if you have multiple connections open AND keep PL/SQL Developer running for a few days. We'll check it out.

That is one way that can make it slow, but not the only way. As stated above it also gets slow pretty quickly in this scenario:
[quote]You get easily slow response times and see lots of sandclocks when comparing half a dozen schemas each with a few hundred objects. Just switching to the PL/SQL Develoepr application takes about 10 sec. Windows then even even detected unresponsiveness and suggested to kill the PL/SQL Developer instance. Some compares also seem to have hung up completely and don't seem to move forward anymore. Switching from one compare window to the next also already takes many seconds.[/quote]
I actually just used 3 schemas, so 3 different connections, i.e. schema A, B, C. I was comparing A with B, B with A, A with C, C with A, B with C and C with A. This got me annoyingly slow response times in just a couple of minutes.
Are you still unsuccessful in recreating any slow response scenario? Is there anything we can still do, to help you figure out the reason for this issue? Is the any way to figure out what PL/SQL is doing, when it's in its slow response mode and how it ends up getting there?
Can you give us any indication by when you expect this problem to be solved and make v11 respond quickly enough so that it's worth using it for all the users affected too much by this issue as well?

Marco - I believe that problem appears primary when open multiple connections, no matter how long plsqldeveloper was opened. Ive done my test again now, Ive opened new plsqldeveloper, for one DB, it was quick. Then Ive open windows for another 3 databases and it become slow. Switching between windows takes 2 or 3 s. Plsqldeveloper I had open from yesterday with connected only to one database is still quick. So I believe that main problem will not be with time, but with multiple connections.

Pavel

[quote=PMrb]Marco - I believe that problem appears primary when open multiple connections, no matter how long plsqldeveloper was opened.[/quote]
I tried this scenario: opened 4 database connections over a WAN, opened 3 different windows (SQL, Test, Program) for each connection. Ran various SQL statements and PL/SQL code in each window. Performance remains excellent, switching between windows takes 0 seconds.

Can you let me know your settings from the Preferences > Oracle / Connections preference page?

Now I aggree with Pavel that multiple connections are the problem. Here are my settings from the Preferences > Oracle / Connections preference page:
[Oracle]
SessionMode=0
OpenTransaction=2
CheckConnection=False
SelectedHome=OraClient11g_home1_32bit
OCIFile=
AllowMultipleConnections=True
ConnectionsPinnedByDefault=False
AutoCloseConnections=True
StoreConnectionsHistory=True
StoreConnectionsPassword=True

[Oracle]
SessionMode=0
OpenTransaction=2
CheckConnection=True
SelectedHome=
OCIFile=c:\Oracle\product\12.1.0\client_1\BIN\oci.dll
AllowMultipleConnections=True
ConnectionsPinnedByDefault=True
AutoCloseConnections=True
StoreConnectionsHistory=False
StoreConnectionsPassword=False

So
Session mode - mutli session
logof with open transaction - ask
check connection - check
Oracle home - empty
Oci library - c:\Oracle\product\12.1.0\client_1\BIN\oci.dll

Multiple connections
Allow multiple connections - check
Pin window connections by default - check
Automatically close unused connections - check
Store recent history - empty
Store with password - empty

[quote=Marco Kalter]switching between windows takes 0 seconds[/quote]
Switching between program windows has never taken 0 seconds for me. At least not in the same way that switching between tabs in Notepad++ or Excel or any other program takes 0 seconds. Perhaps they all take <1 second, but PL/SQL Developer is noticeably slower. If that's not the case on your computer, maybe that's related to why you can't reproduce some of the other problems.

I've always blamed the slowness on PL/SQL Developer refreshing parts of the GUI that it doesn't need to. For example, when I switch between two blank SQL windows I can see a flicker in my Object Browser tab as if it's refreshing that as well (and from network traffic mentioning "last_ddl_time" I believe that it is). Since the Object Browser has its own refresh button, I don't understand that.
Other times when opening a new sql window I can watch PL/SQL Developer un-maximize the current window, open the new window un-maximized, and then maximize the new one. I don't see this when switching windows, but if it happens there too (just too fast for me to notice) I'm sure it adds a delay.

Alright, I have the following reproducable test case:

1. Open pl/sql developer without connecting to a database
2. Open two SQL windows
3. Un-maximize the SQL windows (for easier observations)
=> switching back and forth between the two SQL windows by clicking them takes about 0.2 seconds

4. connect to a database (connections panel, right-click "connect as main")
=> switching back and forth between the two SQL windows by clicking them now takes about 1.0 seconds

5. session -> log off -> all
=> switching back and forth between the two SQL windows by clicking them still takes about 1.0 seconds
(note: the SQL windows still show the connection in their status bars, even though they're supposedly disconnected)

6. change connection -> disconnect in the two SQL windows status bars
=> switching back and forth between the two SQL windows by clicking them now takes about 2.3 seconds, and another 2.0 seconds before the cursor actually stars blinking.

I don't know how this relates to what others are experiencing, but hopefully it helps track down at least one of the problems.

I tried "OldLocking=1" but it did not make a difference.

Version 11.0.2.1766
Windows 8 (64-bit) 6.2 Build 9200
"C:\Program Files (x86)\PLSQL Developer\plsqldev.exe" nosplash nologon instantclient="C:\Program Files (x86)\Oracle\instantclient_11_2"

Unfortunately this does not reproduce the issue for me. Window switching is always instantaneous.

To obtain some more diagnostic information, can you modify the shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" DebugSQL

Redo the steps above and send me the debug.txt file that is generated in the PL/SQL Developer directory or in the %APPDATA%\PLSQL Developer directory (e.g. C:\Users\<User>\AppData\Roaming\PLSQL Developer).

Done. debug.txt and analysis sent to support@allroundautomations.com

Thanks. We have received it and will check it out.

Debug send. I had opened two plsqldevelopers, one with connection only to one database, second one with connection to 3 databases (or something like that), first one is quick, second one slow, hope that youll see this in debug.txt Ive send to you.


Pavel

Can all users with this performance problem try the following preliminary patch release?

http://www.allroundautomations.com/download/plsqldev1102.1768.exe

We were able to fix the performance problem with the help of a forum member and would like confirmation that this does indeed resolve the issue for all affected users.

Thanks in advance!

Hi Marco. Im testing it from morning and it looks fine. Ill try to test it today and tomorrow and let you know then, but on first sight speed looks OK.

Edit - after one day testing speed is OK. Ill let it run whole night and let you know tomorrow if anything changed.

Maybe just one thing - it looks like that when Ill switch from sql window to another sql window that not just window list is refreshed, but icons on Objects windows blink so I think that they are refreshed too? On 10 this work differently, there was no refresh, so switching was little quicker. Its not big delay, its in microseconds I think, but maybe you can look onto this too in future if there is no big plan behind it why this must be done.
Anyway when Ill switch in window from sql to output this refresh of icons in Objects isnt done, so it looks like refresh is done only when switch between window list.

Edit2 - speed looks fine even today, so from my point of view new version can be released.

Pavel

Hi Marco, I'm testing the new version since this morning and so far it looks a lot more responsive and hasn't been falling into this "unusable due to unresponsiveness mode" anymore. I guess it's still too early to confirm the fix, but I'll keep you updated.

One minor issue exists still: When I have a larger project open with about 60 window list items and I click on another item, the window for the new item apprears pretty quickly, however the highlighting in the window list items takes about a second. This behaviour is irritating and should still be fixed as well.
With just a few items in the list the appearance of the new window and the highlighting in the window list items seem to be less than 100 ms apart.

Hi Marco - I agree with Bernhard, this highlighting is little annoying and it will be nice if you repair this part too. Anyway when will new version be available as standard, not just preliminary patch? Can you give us some update?

Pavel

We'll check out the window list issue.

We'll have a final 11.0.3 version available when we have enough assurance that the performance issue is fixed. Unfortunately has been little feedback so far.

I think it's safe enough for me to confirm, that the performance issue is fixed. I've been using the latest version all the time and it seems to be at least as responsive and stable over longer time in responsiveness as v10 again.

I agree with Bernhard. I'm using this version from day you gave it to us and I have no problem with response. When I try to use the standard 11 version I have that response problem even now. So from my point of view response problem was repaired in this new test version you've gave as and can be released as standard version. OK, maybe you can repair that highlighting too, so new version will be even faster and it will be nice if this will be repaired in that 11.0.3 version too so we can install this to our users as final version.

If youll need some other tests from us to be sure that problem was repaired let us know.

Pavel

Testing version 1768
About 40 windows are opened (2 databases)

When I switch windows the contend is shown almost instanly but the window is unusable for 2-3 seconds. And Window List is updated after 2-3 seconds.
This lag also happens when the Window List is hidden so it doesnt seem like rendering issue.
Build with this issue cant be pushed to production, I guess.

We can indeed reproduce the Window List issue when many files are opened. We want to fix this as well for 11.0.3. We hope to have a test version for this shortly, which will posted here too.

For me the performance of switching windows in 11.0.2.1768 is OK.

Hi Marco. When you expected new version? We have open project here to give users plsqldeveloper instead of other application, I dont want to give them plsqldeveloper 10 when there is 11, but on the other side I have some terms, when I must start with this project and that date is almost here. So I need to know when new repaired version will be available. Thanks Pavel

We are working on some final optimizations and hope to have an 11.0.3 version available next week.

When I open an empty project with parameter "nologin", it still takes about 2..3 seconds before PL/SQL Developer v11.0.2.1768 responds to any menu selection. What is it still busy with then?
Could this response time be shortened as well or at least a sandclock be shown until it's ready to really respond? Thank you.

This effect is unchanged in v11.0.2.1769

Can you guys try this new preliminary patch release? It should fix all performance issues.

http://www.allroundautomations.com/download/plsqldev1102.1769.exe

Please post your findings here...

For me it works a lot like the 1768 build. Opening, closing, and switching windows things still take fractions of a second longer than I wish they did (none of it is instantaneous) but I think this is as fast as it has ever been.

Transaction indicator still has some negative effect on rendering perfomance. It also overlaps with window connection indicator.
But the performace is all good overall.

From my point of view everything is quick enough (Im using it from the day you gave as that 1769 version), so you can release it as new version.

Pavel

Hi Marco

When new version will be available? You said that it will be available last week, which obviously didnt happen, so whats new term? We will need it soon, because Im not able to delay installations there any more, so if it will not be available lets say tomorrow or sometime like that Ill start to install plsqldeveloper 10 to our users. So please let me know. Thanks

Pavel

Version 11.0.3 will be released tomorrow.