... but only in strange circumstances...
I encountered some strange behaviour while running UD and Seti together on my Workstation.
Here's the system setup:
Athlon XP 2700+
1 gig ram
Linux 2.6.0 (Gentoo)
VMWare 4.0.5 (10 gig virtual hdd, 640 meg virtual ram)
I boot XP on the vmware image.
Anyway, I have just set up this box to run seti under the linux half as well as UD under the VMware half. I have set both the setiathome and vmware processes at nice 19. (the idle processor time is divided exactly between the two processes).
Because UD judges your computer's rating by more than just the proc speed, if you cut the proc speed in half (essentially what I've done here), the computer rating does not fall in the same line. UD used to give my virtual computer approximately 160... now it gets 113 for a drop in cpu speed of 50%.
I'm crunching seti and ud, and the computer is achieving more than what would be expected. The half devoted to UD is producing more than 2/3 of what the computer would have normally produced (rating * time spent).
I don't consider this cheating, as the UD behaviour is by design (rating by more than just processor speed). That plus I am only doing this while the seti team needs help...
I encountered some strange behaviour while running UD and Seti together on my Workstation.
Here's the system setup:
Athlon XP 2700+
1 gig ram
Linux 2.6.0 (Gentoo)
VMWare 4.0.5 (10 gig virtual hdd, 640 meg virtual ram)
I boot XP on the vmware image.
Anyway, I have just set up this box to run seti under the linux half as well as UD under the VMware half. I have set both the setiathome and vmware processes at nice 19. (the idle processor time is divided exactly between the two processes).
Because UD judges your computer's rating by more than just the proc speed, if you cut the proc speed in half (essentially what I've done here), the computer rating does not fall in the same line. UD used to give my virtual computer approximately 160... now it gets 113 for a drop in cpu speed of 50%.
I'm crunching seti and ud, and the computer is achieving more than what would be expected. The half devoted to UD is producing more than 2/3 of what the computer would have normally produced (rating * time spent).
I don't consider this cheating, as the UD behaviour is by design (rating by more than just processor speed). That plus I am only doing this while the seti team needs help...
Facebook
Twitter