• 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.

Quick OGR Question

quick answer: 8-12 hours (edit: PIII 500)

Long answer: OGR stubs vary a lot in length. You caould easily get stubs that range from 30 gnodes - 300 gnodes. The average stub size for OGR 25 seems to be somewhere between 100 and 120 gnodes, depending on who you ask. You can use the team anandtech speed calculator to calculate how many gnodes you can do in a day.
 
Ok, that makes me feel better. It takes me about 6-7 hours to crack one. I was kinda worried I was doing something wrong. I guess I'm just used to RC5.

The calculator says I should be doing about 361 WUs per day and that seems about right.

Do you know if there is anything that I can do to help speed that up short of buying new parts.

CetiAlphaV
 
My K6 233 just took 23 hours to do a 127 Gnode stub, which is about average size.

The largest OGR-25 stubs are about 450 Gnodes, so that is one reason I use checkpoints on my OGR crackers, and don't run OGR on slower machines.

viz
 
If you have a P6 processor, the new beta client gives a VERY nice speed increase. Other than that, there isn't anything that wouldn't also help RC5.

The most obvious cycle stealer: OpenGL screensavers take up a lot of processing power, and all screensavers take up some cycles, a blank screen is best.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top