I'm looking at SetiWatch and I see several of my clients running much lower than what they should. I've got a P233 looking at 42 hrs to complete. I've got 3 P2-300's that are looking at 22 hrs. I'm using the 2.70 (beta) client and I understand that completion time varies a lot more than the 2.4 client. The 2.70 client seems to be great for faster machines but a bad option for slower boxes. I'm probably going to load the 2.4 client back on these slower (less than P2-350) machines just for more stable times.
That said, is this wrong? Should I run the 2.70 beta client because it produces the WU the fastest? Should I be running the 2.4 client instead of the 2.70 beta because it's the latest public client available? Should I always run the latest (official) client available even if it's slower than a previous version? What if 3.0 comes out and it doubles the WU time? How many of us will switch from 2.4 or 2.70B if 3.0 takes twice as long to finish?
Should Seti@Home require the latest client be used to analyze data? I dunno. I'm all for the stats but this is a scientific project. I'm sure SETI just wants the best data available. I'm rambling and need to get back to work...
Rob
That said, is this wrong? Should I run the 2.70 beta client because it produces the WU the fastest? Should I be running the 2.4 client instead of the 2.70 beta because it's the latest public client available? Should I always run the latest (official) client available even if it's slower than a previous version? What if 3.0 comes out and it doubles the WU time? How many of us will switch from 2.4 or 2.70B if 3.0 takes twice as long to finish?
Should Seti@Home require the latest client be used to analyze data? I dunno. I'm all for the stats but this is a scientific project. I'm sure SETI just wants the best data available. I'm rambling and need to get back to work...
Rob
