All BOINC-projects is struggling, so while it looks like TAS is planning to run Einstein@home in April, my guess is CPDN will be chosen to run in May or a couple months later.
If so, would actually recommend a deviation from the normal deployment in TAS, run both Einstein@home and CPDN over two months, in April & May.
Reason? Einstein@home is very fast on Amd-XP-cpus, while CPDN is excellent on Intel-cpus and Amd64.
Intel-cpu's is awful in Einstein@home, much slower than comparably-clocked Amd's, and some reports claims HT has zero effect.
Intel-cpu's is excellent in CPDN for BOINC under windows due to the Intel-compiler, Amd is slower here.
Amd64/Opteron is mediocre in Einstein@home and good in CPDN, so would recommend these cpu's to run CPDN.
So, in case the TAS-members as a total has roughly 50/50 amd & intel, it's much better for both projects to split the computers between the projects, than run Einstein@home in April and run CPDN later this year.
If so, would actually recommend a deviation from the normal deployment in TAS, run both Einstein@home and CPDN over two months, in April & May.
Reason? Einstein@home is very fast on Amd-XP-cpus, while CPDN is excellent on Intel-cpus and Amd64.
Intel-cpu's is awful in Einstein@home, much slower than comparably-clocked Amd's, and some reports claims HT has zero effect.
Intel-cpu's is excellent in CPDN for BOINC under windows due to the Intel-compiler, Amd is slower here.
Amd64/Opteron is mediocre in Einstein@home and good in CPDN, so would recommend these cpu's to run CPDN.
So, in case the TAS-members as a total has roughly 50/50 amd & intel, it's much better for both projects to split the computers between the projects, than run Einstein@home in April and run CPDN later this year.
Facebook
Twitter