Posts by Jon Connell

1) Message boards : News : Heavy I/O on Windows WUs (Message 26971) Posted 9 Nov 2014 by Jon Connell Post: I think I may be seeing the same "w-" thing here. Not entirely convinced its LHC code to blame here though - neither am I sure its the high IO rate to blame. No need for a direct response to this unless something jumps out at you... Hopefully the following may help: Me: ID: 332140 Win 7 box, i7-2600K CPU @ 3.40GHz, NVIDIA Quadro FX 580 512MB. BOINC 7.2.42 Running SETI@, COSMOLOGY@, EINSTEIN@, MILKYWAY@ and LHC@home 1.0. Symptom is BOINC throws multiple ERROR windows and CLOSE PROGRAM windows after a few minutes. New behavior that I "think" is associated with LHC - I can't definitively prove that statement though. Seems to be associated with these recent LHC work units is the best I can say. FYI - your IO reads are running around 800 in the file manager - compare to 14 for a Cosmology@ app and 2000 plus for a Seti Astropulse app as each cycles through processing. Memory usage is 23.5k for the LHC App - compare to a mighty 100k thru 370k for a typical Cosmology@ executable. Nothing obviously out of line in your resource usage from where I sit then. Only thing that looks at all funky is that both Sixtrack and Cosmology@ stay resident in memory when the screen saver exits - something I have told BOINC not to do in my preferences... That may or may not be related to the error I am seeing here of course. Bottom line if the units are coming in good at your end then I can deal with the error windows - system appears to continue working through the multiple error windows anyway. Thanks for your efforts.

LHC@home