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