High CPU when using Excel with conditional formatting

[greenfingers]

Hi, this isn't a problem directly to do with BA but I wonder if anyone out there can help! I have a really simple Excel spreadsheet connected to Gruss and was getting really high (average 25% but goes higher) CPU for Excel alone showing in my Task Manager.

I realised that it wasn't actually the workbook connected to Gruss that was causing the high CPU but another workbook I also have open at the same time which ISN'T connected to gruss, it is 'freestanding' if you like. This other workbook I use for logging the results of each market I trade and has loads of other info. Here's the thing I found, the high CPU is being caused by the conditional formatting I have on this sheet.

If I don't have Gruss connected to the first workbook, this CPU issue doesn't happen. Also, if I switch to a blank sheet in the workbook with the formatting then it doesn't happen.

It's as if by having one workbook updated by Gruss, Excel is taking it upon itself to re-evaluate all the conditional formatting in the other workbook too, even though that workbook isn't connected to Gruss!!!!

Hope this makes sense, it's really annoying because my CPU is maxing out at 100% sometimes during races which is a bit hairy!

Anyone know how I can stop Excel from evaluating the conditional formatting in this spreadsheet whilst it's not actually being edited???! I could switch to a blank sheet before every race, but I'd rather solve the problem! Any ideas, please:?:

[silver]

Try opening the 'problem' worksheet in a second instance of Excel and in the options, set calculation for that instance of Excel to manual. That should prevent recalculation in the Gruss sheet (which is presumably set to automatic calculation) from prompting recalculation in the 'problem' sheet, which is what I think may be happening.

In the instance of Excel set to manual calculation you could use code to get it to manually calculate at set intervals - every 5 secs, 30 mins whatever. That would leave calculation 'automated' within that sheet but reduce the CPU load. Otherwise you can just manually make the sheet calculate when necessary.

[greenfingers]

Hey thanks for your reply Silver! I never even thought of opening another Excel instance, doh! Maybe it's my Macintosh upbringing!

Anyhow, I tried your suggestion and you already had the solution at halfway! The problem is solved by having the workbook with the conditional formatting open in another Excel instance - even with automatic calculation turned on the CPU problem no longer occurs.

Many thanks, you've saved me a lot of head scratching and CPU overloads!

[silver]

Happy to hear that, Greenfingers.

Glad you haven't had to compromise your conditional formatting, I'm a big fan of it myself

[greenfingers]

Yup, I've got 31 'conditions' on that sheet. It just wouldn't be the same without them!!!

CPU is now about 5% for the workbook linked to Gruss and 0% for the other. I've got enough CPU left over to run my screen recording software and still have plenty to spare. Result!