I'm running with cuda:operations=8192 and filter:runlength=8192 now. I do for sure notice that the computer is under heavy load... :) Chains/s seems to go a bit above 152/s. But why is this rate rising from the start to later stabilize? Are the other parameters for the hardware autodetected, or should I try adjusting anything more?
My card is not overclocked, but can playing with these performance parameters also give me wrong values? As there is not that much messages on this list, I hope it's ok to be a bit lazy and ask newbie questions without reading up or trying out everything on my own... -Terje 376362 chains done, current rate: 153.49 chains/s Is there a way do check total chains done? On Thu, Aug 27, 2009 at 3:44 AM, Sascha Krissler <[email protected]>wrote: > > > I just installed the software and ran my first test with --chains > > 1024. The wiki mentions that that result can be checked. Anyone? > > make a trac ticket, send the data to me or verify for yourself as described > in > the link below. > > > > > Also I'm not sure about how to get the most out of my graphics card ( > > GTX280). I used cuda:operations=1024 in my test and found my computer > > usable with that. The timings for that run was this: > > take a look at > http://reflextor.com/trac/a51/wiki/RunningTheProgram > be sure to make runlength at least equal to operations and then find the > optimal value for your setup. mine was 8192 on a headless gtx260, this > should be a good start. > > > > > But what are the optimal settings to use when I'm not using the > > computer? > > > > And one last thing.. If I have to stop the table generation, is it > > just to start it again or do I have to adjust parameters or anything? > > > > use the same command line, the append option of --consume appends > the data to the existing table. > there will be support for changing the operations parameter of a running > process when i find the time to implement it. > i would love to hear from any benchmarking you made. > if you overclock your GPU be sure to check the computed chains against > reference data, because they compute wrong values when clocked too much. > again there will be a more easily usable version to automatically try the > overclocking when i find the time. > ________________________________________________________________ > Neu: WEB.DE Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate > für nur 19,99 Euro/mtl.!* http://produkte.web.de/go/02/ > > _______________________________________________ > A51 mailing list > [email protected] > http://lists.lists.reflextor.com/cgi-bin/mailman/listinfo/a51 >
_______________________________________________ A51 mailing list [email protected] http://lists.lists.reflextor.com/cgi-bin/mailman/listinfo/a51
