As to the processor, I upgraded the computer in March. Before that I had a Pentium 4, 1.7 mhz with only 512 MB RAM. That could account for the low RAC.
Your previous computer is listed under a completely separate host ID so its stats are not at all reflected in the RAC of your current host. The Q6600 has been crunching for a month so your RAC should have pretty much reached a plateau by now.
Quote:
It seems I have been limiting the CPU to 2 processors but with no suspension when I'm on the computer. However, I'm still getting Seti but no Einstein.
Have you increased the preference to allow all 4 CPUs to crunch? With the 1/3 resource share for E@H, at least one CPU should always be doing E@H work if all 4 were available. If you set your resource share to 50/50 you would get a nice balance of 2 CPUs crunching each project. If you were to investigate the optimised app that is available you could also get a significant speedup in your E@H crunch times as well. Of course there's a bit of work to read up on what is available and more need to pay attention to future developments if you choose to use an optimised app.
RE: As to the processor, I
)
Your previous computer is listed under a completely separate host ID so its stats are not at all reflected in the RAC of your current host. The Q6600 has been crunching for a month so your RAC should have pretty much reached a plateau by now.
Have you increased the preference to allow all 4 CPUs to crunch? With the 1/3 resource share for E@H, at least one CPU should always be doing E@H work if all 4 were available. If you set your resource share to 50/50 you would get a nice balance of 2 CPUs crunching each project. If you were to investigate the optimised app that is available you could also get a significant speedup in your E@H crunch times as well. Of course there's a bit of work to read up on what is available and more need to pay attention to future developments if you choose to use an optimised app.
Cheers,
Gary.