"Steve Charlton" <steve@nospam.freeserve.co.uk> wrote in message
news:a6Ui3FWn+E4AFw6e@smokering.freeserve.co.uk...

I'm trying to run both at once, however ClimatePrediction has hardly
slowed down and Boinc hardly runs at all. Is BOINC being too friendly
and releasing control before its 10ms are up or is ClimtePrediction
being too greedy and maybe running multiple threads or running at the
wrong priority level or something? Anyone know?
-- 
Steve Charlton                  |There may be intelligent life on other

planets

steve@gnirekoms.freeserve.co.uk |in the galaxy, but somebody, somewhere,

had to

sdrawkcab=backwards             |be first.
                                        Carl Sagan (sadly missed)

If running an HT'd machine, you can set BOINC to run w/1cpu, and then run
the non-BOINC CPDN concurrently, and each process will take exactly 50%, as
shown in the tskmgr.

This is how I run. It is NOT an elegant solution. It DOES work.

IIRC, non-BOINC CPDN runs @ windows priority level '4', and BOINC
runs @ '2'. Somebody, correct me if I'm mistaken.

This may be why you see CPDN stomping BOINC. Then again, CPDN
will be under BOINC soon, so BOINC's proj prefs should resolve the
issue.

But for now, my solution suits me fine. Maybe not, somone else, though.

Oh yeah...w/this set-up, if either proj fudges up, the other kicks in at
100%, allowing for no loss of machine cycles.
-- 
Strat