Can you guys try this version with the DebugSQL option as before? It contains some extra diagnostics. Please send me a new debug.txt for any query performance related issues.

The issue with the excessive number of v$nls_parameter queries is already fixed in this version, so that should already help in some cases.

Hi Marco

I just emailed the Debug.txt file to support@allroundautomations.com.

The 8 second delay is still there, and I believe it is between lines 1695 and 1696 i.e.:

23-Aug-2011 12:56:07 CreateQueryTabs Finding SQL
23-Aug-2011 12:56:15 CreateQueryTabs SQL Found

So it looks like the delay is when it is trying to figure out which SQL to execute.

If you need anything else, let me know.

Best regards

Billy

Thanks. We have all we need to fix this.

Hi!

I ran queries and they are still slow. Now there are no excessive nls thing. I have run the same in ver 8 and 9, in 8 result is instant, but in 9 it takes 5 secs now.
Now it seems that it's executing dictionary info SQL, I have set that off in preferences. Maybe this is the cause.
I sent debug to support mailbox.
Please check.

thanks in advance
Kirurgs

Thanks, we have received it. We'll try to reproduce and optimize this.

This version should fix the query performance issue and AutoSelect SQL performance issue for large scripts.

Hi!

I have tested it and now it seems that result is instant, if dictionary info is checked it's still slow, but I think that's expected. So in short - problem fixed.
BUT for some strange reason now plsqldev.exe process eats whole cpu all the time after connection is made, cpu usage varies from 65% to 99%.

regards
Kirurgs

I am having the exact problem. When using version 9 and connecting, it runs this query even though I have selected to use DBA_views where available. This sorted the same issue in version 8, but does not seem to work in version 9.
The query is this:
select s.synonym_name as object_name, o.object_type
from all_synonyms s, sys.all_objects o
where s.owner in ('PUBLIC', :schema)
and o.owner = s.table_owner
and o.object_name = s.table_name
and o.object_type in ('TABLE', 'VIEW', 'PACKAGE','TYPE', 'PROCEDURE', 'FUNCTION', 'SEQUENCE');

We are on 11gR1. Due to this we are not installing version 9 since the CPU is so high and will bring our environments down due to the amount of users we have.

[quote=Kirurgs]BUT for some strange reason now plsqldev.exe process eats whole cpu all the time after connection is made, cpu usage varies from 65% to 99%.[/quote]

Does the CPU usage go down eventually?

Can you test what happens if you go to Tools > Preferences > Code Assistant and disable the "Describe Context" option? Does this clear the CPU usage after a restart?

[quote=lparker]I am having the exact problem. When using version 9 and connecting, it runs this query even though I have selected to use DBA_views where available. This sorted the same issue in version 8, but does not seem to work in version 9.
The query is this:
select s.synonym_name as object_name, o.object_type
from all_synonyms s, sys.all_objects o
where s.owner in ('PUBLIC', :schema)
and o.owner = s.table_owner
and o.object_name = s.table_name
and o.object_type in ('TABLE', 'VIEW', 'PACKAGE','TYPE', 'PROCEDURE', 'FUNCTION', 'SEQUENCE');

We are on 11gR1. Due to this we are not installing version 9 since the CPU is so high and will bring our environments down due to the amount of users we have. [/quote]
You can change or remove these queries by editing the CANames.sql file in the PL/SQL Developer installation directory. The file includes a description.