SV: RE: High CPU editing large package

Hi Michael,

 

"Check syntax as you type" is disabled (It doesn't make a lot of difference if it is enabled or not)

 

After i stop typing the cpu goes to normal after 2 secs.

 

You are right that the thread is running on a low priority, and apparently it doesn't affects the typing.

 

I was just wondering what was the cause for the high cpu.

 

Let's just leave it for now.

 

 

By the way. I run toad on a rather old 1.83 GHz dual core notebook

 

Thanks for your reply,

 

Best regards

Finn

Fra: [email protected] [mailto:[email protected]] På vegne af Michael Staszewski
Sendt: 5. oktober 2011 15:30
Til: [email protected]
Emne: [toad] RE: High CPU editing large package

 






Does the CPU stop pegging when you stop typing? If so, approximately how long after you stop typing does the CPU return to normal? If you have the option Options|Editor|Code Assist|"Check syntax as you type" enabled disable it and try again. Does that make a difference?

 

> It seems that the hole package is scanned when a key is pressed

 

It is, but only after a delay. I believe the delay is 500ms. When you pause the Editor parses the file so that the navigator remains up to date and so that any other features requiring parser results can execute with minimal delay. This process runs in a low priority background thread and aborts when you resume typing. When your CPU is pegged is Toad unresponsive?

 

Michael

 

_____________________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Finn Jalsøe
Sent: Wednesday, October 05, 2011 2:47 AM
To: [email protected]
Subject: [toad] High CPU editing large package

 

 

Hi there,

 

Found a problem in Toad 11.0.0.116:

 

When editing a large packagebody (+6500 lines) the cpu spikes at nearly 100% at EVERY keystroke.

(It seems that the hole package is scanned when a key is pressed ???)

 

I have tried to disable 

"Check Code Analysis Rules as you type" and "Code Insight" but this didn't help

 

 

Any idea of what to disable ??? 

 

This problem wasn't in 10.6

 

Med venlig hilsen

 

Finn Jalsøe

BK-IT

 

Bladkompagniet A/S · Islevdalvej 205 · DK-2610 Rødovre

Tlf: 7020 7225 · Dir. 4451 7171 · Email: [email protected]