Toad World® Forums

Toad Graphics Performance Question

I have a lot of slowness when clicking from one editor tab to another. It looks
like Toad partially draws the next screen, then it pauses, then it completes the
drawing of the screen.

I’m running a dual core 6400 @ 2.13 GHz with 2 GB Ram.

My graphics board is a 6 year old 256MB ATI Radeon X1300PRO

http://reviews.cnet.com/graphics-cards/ati-radeon-x1300-pro/4505-8902_7-31530067.
html

My questions are:

  1. what is the likelihood that a better graphics card would improve TOAD’s
    windowing performance?

  2. Are there any other measures I can take to improve TOAD’s windowing
    performance?

Thanks,

Mike

Performance problems when changing tabs will persist forever as long as we
remain in a multi-tab style, multi-desktop Editor mindset. I proposed (and
implemented) an alternative early in the Toad 11 cycle, but the consensus was to
keep the current design even if it is less efficient and more resource
intensive. Performance under the proposed change was incomparable to earlier
versions. I could load > 400 tabs without error and I forget the exact stats,
but something like 60 or 80 files in less than 20 seconds.

Depending on what version you are on you can expect to see better performance by
upgrading to the latest. Toad 11 should be better than Toad 10.6 in this area
too so if you are able to check out the beta then go for it. I think that
performance gains would be most visible with a fair amount of higher quality,
faster RAM and multi-core CPU. Toad isn’t a graphics intensive application so
the graphics issues are likely a combination of less than stellar code in this
area of the product and the intensity of the code required to manage the various
tab styles.

Michael

Sorry they didn’t go with your proposal. When I click on a tab, or button I
want something to happen NOW, not 3 seconds from now. I know that as a developer
it’s always a compromise between features and performance. I would gladly
sacrifice many of the window style options for performance.

Eye candy, of course, helps sell a product, but when resizing the window takes
literally 5 seconds then ( add your explicative here).

I’m on 10.6. Looking forward to Toad 11 ! :slight_smile:

Regards,

Mike

On Thu, May 5, 2011 at 10:25 AM, Michael Staszewski <
michael.staszewski@quest.com > wrote:

Performance problems when changing tabs will persist forever as long as we
remain in a multi-tab style, multi-desktop Editor mindset. I proposed (and
implemented) an alternative early in the Toad 11 cycle, but the consensus
was to keep the current design even if it is less efficient and more
resource intensive. Performance under the proposed change was incomparable
to earlier versions. I could load > 400 tabs without error and I forget the
exact stats, but something like 60 or 80 files in less than 20 seconds.

 

Depending on what version you are on you can expect to see better
performance by upgrading to the latest. Toad 11 should be better than Toad
10.6 in this area too so if you are able to check out the beta then go for
it. I think that performance gains  would be most visible with a fair
amount of higher quality, faster RAM and multi-core CPU. Toad isn't a
graphics intensive application so the graphics issues are likely a
combination of less than stellar code in this area of the product and the
intensity of the code required to manage the various tab styles.

 

Michael

The number of opened tabs affects things a lot too. Do you typically work with
many tabs? Toad 11 is much better in the performance department when the number
of tabs increases. As always though there is some upper limit. I’m not sure what
it is, but having a couple dozen tabs opened in the Editor will likely slow it
down.

Indeed I do generally have a lot of tabs open. Generally between 10 to 18. Does
it matter the number of tabs per session? Would I get better performance by say
having 4 sessions open, each with 5 tabs verses 1 session with 20 tabs?

Mike

On Thu, May 5, 2011 at 12:23 PM, Michael Staszewski <
michael.staszewski@quest.com > wrote:

The number of opened tabs affects things a lot too. Do you typically work
with many tabs? Toad 11 is much better in the performance department when
the number of tabs increases. As always though there is some upper limit.
I'm not sure what it is, but having a couple dozen tabs opened in the
Editor will likely slow it down.

Shouldn’t matter really. A tab is a tab and each should use the same amount of
resources, but if you see that it does make a difference and you can work in
that way then go for it.

In my IDE I start to sweat if I get more than 4 or 5 tabs open. If I have to use
the little arrow to scroll to non-visible tabs then I generally close my project
and come up with a new game plan. :slight_smile:

If I have to use the little arrow to scroll to non-visible tabs

then I generally close my project and come up with a new game plan. :slight_smile:

Ditto. However… sometimes you just don’t have the option. For
example, we have modularized functions. And if you run into an issue
“several layers deep”, you might not have any choice but to have
quite a few tabs open.

Normally, while I’m developing, I don’t have any more than 4 tabs
open. 1 for the spec, 1 for the body, 1 for text (notes) and 1 for general sql
queries, snap code validation, etc.

But every once in a blue moon, I’ll be troubleshooting a bug and have to
debug down through several packages to figure out exactly what’s going
wrong.

Caveat: I don’t have an issue with performance, just giving an example
where one might not end up with an option of having several tabs open.

Roger S.