• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

This could explain a few things going on at Dnet

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
hmm, looks like you only have one core for each project, RC5 and OGR, thats too bad. Guess that doesnt leave you with any options but to run core 0 on each CPU.
 
It might be more worthwhile to run SETI on some of those CPUs. I don't know what kind of client the SETI@Home folks have for that bad boy (or even if they do have one), but I know the heavy irons tend to really excel at SETI...

JHutch
 


<< Automatic processor type detection failed. >>

No, that means it didn't automatically find the right one.
Obviously those cores haven't been ported to yet.
You might go into the dnetc -config and manually select and try to bench every core that is listed.
 
yeah with the -bench it tries 2 core allitnil and lintilla and they both suck. 5,3xx keys/sec

I'll consider the seti option for that whale.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top