Very Slow responsiveness when working with off shore sites

[Saar]

Hi,

Our plsql developer version is: 12.0.4.1826 (64bit)

I would like to raise an issue with plsqldeveloper that might be relevant to other programmers and make developers/dbas lives somewhat harder. I'm referring to the "hangs" that occurs every-time the tool tries to, probably, read information from remote site for "smart completions" and other behind the scene tasks. This does not occur for on premise servers (geographically near you).
When it occurs:
1. Code completion - most annoying (when you type one of the following characters: '.,(', but their might be others.
2. When clicking on an output field - real slow.

My point is, there should be someway to minimize the "network round-trip" that is done when the SQL editor tries to assist. I tested SQLDEVELOPER from Oracle and it seems that they tackle this specific issues quite well, so it is do-able. The problem is: we love PL-SQLdeveloper programming tool, and we would like to make it even better.

For the short term, please consider:
* a property options to disable "output field" smart enhancement - I really have no clue what is being done when I click on an output field with my mouse, but it takes few seconds (~ 10sec or more) to just receive back the control.

For the long term:
* Better responsiveness of SQL editor when working with off shore sites - better responsiveness.

The other issues raised in topic: "Bugs and Enhancement Requests for PL/SQL Developer 12.0.3.1821 (32-bit)" are valid points to consider.

Thanks
Saar

 

[Marco Kalter]

If your network performance is poor, you can make the following optimizations:

Go to Preferences > User Interface > Code Assistant and disable the "Automatically activated" option. Now you have to press F6 to invoke the code assistant, and typing "." "," and "(" will no longer cause a delay.

Go to Preferences > SQL Window and disable the "Show dictionary information in result grid". Clicking on a cell in the result grid will no longer cause a delay in this case.

 

[Bhupen]

+1

I specially feel the pain when clicking on the results grid to edit.
For "." I generally type thru' so the code assistant is not activated in cases when it is not required. I would love to use these options as they increase productivity and workarounds like F6 are not a pretty options.

Thanks!

 

[malinow]

Hi Marco,

I have both options disabled. It works better indeed.

But there is still performance issue when I select the item from the code assistant. Do you have maybe the remedy for this as well ?

Regards,
Marcin

 

[Marco Kalter]

If you have the Code Assistant option "Use original case if possible" enabled, you should probably disable it. In this case the Code Assistant will determine the exact declaration from the database source before inserting it.