high cpu usage when connecting RDP

[adrianzagar]

Scenario:
- log in on client computer (locally) and open pl/sql developer. log in, do stuff, open several windows.
- lock workstation
- connect from another pc using remote desktop client (Microsoft) with the same credential (in order to connect to the same windows session)

What happens: PL/SQL Developer is using 20-30% of CPU and in fact is blocking everything. If you have patience, in 5-10 minutes everything's back to normal, including pl/sql developer.

Any workaround?

 

[Marco Kalter]

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

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

Reproduce the problem and send me the debug.txt file that is generated in the %APPDATA%\PLSQL Developer 12 directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer 12).

 

[Jeff Kandt]

I don't know if this is what you're experiencing, but often connecting via RDP (at least in my case) involves resizing the desktop to a new monitor configuration, which involves Windows messaging all of the running applications to resize themselves. The user doesn't gain control back until that entire process is complete.

PL/SQL Developer seems slower than most applications to react to a change in screen size, especially when many windows are open. Often in multiple document mode I can see it churning through all of the opened sheets, and sometimes it happens slow enough that you can actually see the individual sheets appear to Restore and then re-Maximize themselves.

(And then of course the change in monitor dimensions causes all of your existing crash recovery files to be abandoned, but that's a separate complaint that's never been officially addressed, AFAIK.)

 

[koja]

That's my experience too and indeed the more windows you open in pl/sql developer the slower it gets.

Actually performance is one of the very few areas where if you ask me PLD doen't really shine. Five stars for me when that is finally solved...

 

[IvanZ]

Sadly, it's the downside of the chosen framework which is really unoptimized and far from contemporary platforms.