Is sqldeveloper 1.5.1 clunky?

Question

I just upgraded/installed to 1.5.1 from 1.2.0 on win XP Pro with the latest JDK and it just seems slow and clunky.
It seems to hang up if you let it sit for a few hours, it doesn't even have to be connected to a database for this to happen. If I log into one of our 10.2.0.2 databases as system and try to bring up the tables from another schema it takes forever. The insight or completion (whatever it's called) doesn't seem to work. F4 (what used to describe a highlighted object) doesn't work anymore. Just seems like the older version's features were better. I do like the easier migration from Access to Oracle, but that's all I've found with this version that I like. Other wise it seems too clunky and sluggish. Is it just me?

Answer 1

I see, is your SYSTEM table DMT (Dictionary Managed
Tablespace) or LMT (Locally Managed Tablespace)?
See this if you need to educate yourself on this:
http://www.orafaq.com/node/3.
It may seem pretty trivial and this isn't recommended
for a PROD ENV at this point in time for you but it
could make a difference in response times.
-TimI'll try the control break thing.
I'm curious though as to what difference it should make whether or not my SYSTEM tablespace is an LMT or DMT? That shouldn't have any impact on a select to find table names. As a matter of fact, I just connected as a schema owner in that same database that has all of it's objects in two LMTs and tried expanding the Tables folder. Same slow response, consideribly worse actually, probably due to that schema having a few thousand tables.
Space allocation operations are impacted by the type of tablespace, but I've yet to find a sql statement that parses differently depending upon what type of tablespace it's dependant objects are using.