There are several new features and options that might be coming into play that
did not translate well from your 9.7 installation. Did you upgrade or install
side-by-side?
And don’t forget the toad tuning advisor under the help menu – often
it will tell you which options you have turned on that cost more to process
– and quick links to turn them off J
Glad to see I’m not the only one experiencing this. My Toad 10.1 install from a few weeks ago is S-L-O-W compared to Toad 9.7. I did the Advisor in the help menu as suggested, but nothing of substance.
Examples: It now takes a full minute (I timed it) to bring up Toad the first time. This is with a minimum of other apps running on a machine that has not significantly changed since my Toad 9.7.
If I open a second Toad session, oh boy…my system locks down with the appearance of nothing happening. I can wave my mouse pointer around, but EVERYTHING is frozen for the requisite minute or so.
Occasionally my PC will freeze like this for 10 to 15 seconds even without trying to start another Toad session. None of this happened until the Toad 10 install.
Like Alison, I have Windows XP SP3 with 2GB RAM. I did in upgrade from 9.7. I’ve been using TOAD for about 8 years; never seen one slow things down this much.
As far as I can remember it was a side by side install?
Its difficult to give a particular example it seems to be everything, even just
accepting a parameter into a piece of sql takes long enough to say what’s
happening where as in the other version its almost instant. Running the same
piece of sql in 9.7 and 10.1, 9.7 takes 25 seconds and 10.1 takes about a minute
and a half. It seems to be getting the parameters in to the sql that takes the
time.
Have you investigate the slow startup time using the DEBUG=1 setting in your
Toad.ini, restarting toad, then checking under the Help menu? It will show
everything Toad does on startup, which includes downloading stuff from the web
now…
Also check to make sure you add Toad to the exceptions list in your anti-virus
software.
Jon
On 2/17/2010 11:22 AM, Jeff Smith wrote:
Have you investigate the slow startup time using the DEBUG=1 setting in your
Toad.ini, restarting toad, then checking under the Help menu? It will show
everything Toad does on startup, which includes downloading stuff from the
web now…
Glad to see I'm not the only one experiencing this. My Toad 10.1 install from a few weeks ago is S-L-O-W compared to Toad 9.7. I did the Advisor in the help menu as suggested, but nothing of substance.
Examples: It now takes a full minute (I timed it) to bring up Toad the first time. This is with a minimum of other apps running on a machine that has not significantly changed since my Toad 9.7.
If I open a second Toad session, oh boy...my system locks down with the appearance of nothing happening. I can wave my mouse pointer around, but EVERYTHING is frozen for the requisite minute or so.
Occasionally my PC will freeze like this for 10 to 15 seconds even without trying to start another Toad session. None of this happened until the Toad 10 install.
Like Alison, I have Windows XP SP3 with 2GB RAM. I did in upgrade from 9.7. I've been using TOAD for about 8 years; never seen one slow things down this much.
Previous comments have pointed to an interaction problem with Antivirus
software. Disabling the software reduces Toad startup time to a few
seconds. People have suggested adding toad to an AV's "whitelist" which
should have a similar result.
Hi Jeff–just tried your recommendation. The Toad Memory Usage dialog says:
Page File Usage (Virtual Memory): 68 MB
Working Set Usage (RAM): 72 MB
And the Debug Output window says:
13:12:00 Initializing application
13:12:01 Creating GlobalDataModule
13:12:02 Performing Toad’s startup tasks
13:12:02 Setting Toad help file
13:12:02 Setting global options
13:12:02 Updating license key file with app info
13:12:02 Loading Formatter Plus
13:12:04 Creating main window
13:12:04 Create Bitmaps Form
13:12:05 Restoring dock layout
13:12:06 Checking for Spotlight
13:12:06 Checking for SQL Impact
13:12:06 Initializing Team Coding
13:12:06 Building quick scripts menu
13:12:06 Building external tools menu
13:12:07 Enabling features based on license
13:12:07 Restoring size and position
13:12:07 Ribbit!
13:12:08 Performing Toad’s command line tasks
13:12:08 Application.Run
However, my timing was exactly one minute again from the moment I clicked on the Toad icon to the moment the connections window popped up. As before, I ran this with very few other apps open. It feels like Toad has this big code base that has to get loaded into memory and do a bunch of setup before it can throw up the slash screen and start rendering the desktop.
Good point. We use McAfee here and if I understand Jeff’s comment earlier, Toad is trying to do some connecting to the Internet as it comes up. If so, that definitely might be the cause. Does Toad try to make other connections in the background during operation? It seems to be slow all the way around, even just switching between two open windows like schema brower and the editor.
As far as I can remember it was a side by side install?
Its difficult to give a particular example it seems to be everything, even just
accepting a parameter into a piece of sql takes long enough to say what’s
happening where as in the other version its almost instant. Running the same
piece of sql in 9.7 and 10.1, 9.7 takes 25 seconds and 10.1 takes about a minute
and a half. It seems to be getting the parameters in to the sql that takes the
time.
As far as connecting to the internet, nothing has changed from the previous version, so I’m not sure if that is it. Like previous versions, it just checks for new Toad Tips upon startup, if that option is set. Options > StartUp > “Download Toad Tips once a month” controls it, but that’s been there for quite awhile.
Do you have a lot of other applications running? An Oracle db on the client?
Page File Usage (Virtual Memory): 22 MB
Working Set Usage (RAM): 35 MB
14:27:46 Initializing application
14:27:46 Creating GlobalDataModule
14:27:46 Performing Toad’s startup tasks
14:27:46 Setting Toad help file
14:27:46 Setting global options
14:27:46 Saving QuestKey license
14:27:46 Loading Formatter Plus
14:27:46 Creating main window
14:27:46 Create Bitmaps Form
14:27:46 Restoring dock layout
14:27:46 Checking for Spotlight
14:27:46 Checking for SQL Impact
14:27:46 Initializing Team Coding
14:27:46 Building quick scripts menu
14:27:46 Building external tools menu
14:27:47 Enabling features based on license
14:27:47 Restoring size and position
14:27:47 Ribbit!
14:27:47 Performing Toad’s command line tasks
14:27:47 Application.Run
The queries don’t even have to be running for this to happen! Just seems like the Toad footprint when its running is huge and stepping on the system resources.
I’ve been watching the Task Manager when I do simple things in Toad like open a new connection, close a connection, and bring Toad down and back up. Lots of CPU topping out at 100%, some page swapping, and occasional freezing of other applications while it’s doing the task.