few caveats. been using toad since 1998. I know whats slow and what isnt.
Heres where its slow. Navigating around a screen with cursor. I type but could be 5-6 seconds before what I type arrives on screen.
All other editors on my desktop are fine. PC isnt hanging, this is only in TOAD. I could hold arrow down to scroll a cursor across text but could be 3-4 seconds before cursor moves. Clicking around through packages is fine, navigating through menus is fine.
I have other IDEs, SQL Developer and PLSQL developer on my machine, both dont have this behavior, only TOAD. Developers in house use JS and Datagrip, no issues.
Issue occurs across any instance (I think I have 10 open at the moment)
I had this in last 2 versions, no amount of shutting down or updating TOAD or PC reboots works, behaviour continues. Its not getting any worse but really annoying me now.
Am I missing a button click somewhere? Im applying a boiling frog syndrome to this in that I think its crept up on me and Im now boiling.
What is the file version of Toad.exe? Are you on 17.0.341 or 17.0.353? There was a defect in 17.0.341 where the Navigator panel updates are slow, the panel visually scrolls while reloading, and it slows typing. This was corrected in the 17.0.353 patch. If you are using build 341 then grab the patch. It is available from support.quest.com.
just an update on this, I didnt patch but it has resolved itself. I dont know about anyone else, but I usually operate with up to 10 connections and upwards of 10-15 windows(tabs) per connection. I closed down most of these in an effort to see was it some memory issue threshold and that seems to have resolved.
Now Im down to maybe 3-4 connections with 3-4 tabs on each one and latency issues gone. scrolling is back to normal.
thats the only change Ive made.
Is this expected behaviour? is there a threshold of tabs and connections to be open that would case that?
There's no hard limit, but the more windows (we don't call them tabs) you have open, the slower things get. There's not much we can do about that. The patch will help, you really should get it.
After encountering slow typing issues and searching the forums, it seems this has been a common issue in TOAD since as far back as 2011.
I enjoy the highlighting and auto-completes and all that stuff, so I'm not disabling any of it.
I have noticed that the typing-speed is very dependent on how many other queries you have in your Edit Window, and how CLOSE they are physically to your cursor.
I have about 30 SQL select queries on my editor right now. If I put my cursor between two of them near the top of my window and start typing, only about 1 letter per second appears on the screen.
If I cursor down to the very last line of my edit window and start typing, letters appear in real-time as fast as I type.
If I go back up to the top, between those queries again, and hit return a bunch to create a bunch of white spacing, then start typing, my letters appear MUCH faster than when the nearby queries are closer to my cursor.
So, my solution for now will just be to just create extra linefeeds between my select queries to increase the typing response of the edit window; or just hit ctrl-end to go to the end of my window and type there where response time is the fastest.
It would be nice to not have to do that work-around though because I like keeping my related-queries all nearby each other for organizational reasons. Anyhoo, thought I'd share my debug discoveries regarding this since it's been an issue for over 13 years now apparently :). Thanks!
p.s. I only have 1 database connection open, and 6 edit windows (tabs). Current memory usage is 24MB/32. I'm on Toad 6.2.0.23226 (64 bit)
apologies, I hadn't realized this area was Oracle specific. I'm connecting to an MS SQL database. The Help About says "Toad Data Point". I must just be confused with the different variations of the app I didn't know existed.
