[Sascha Krissler] > to fuel to competition, my GTX260 with 216 cores does 162.54 > chains/s at 691mhz, but since it is headless i do not have to > care for responsiveness.
hehe.. It seems that I have trouble beating that, but I haven't tried running in console mode yet... :) 353348 chains done, current rate: 153.70 chains/s 368757 chains done, current rate: 153.78 chains/s 384007 chains done, current rate: 153.91 chains/s 399530 chains done, current rate: 154.08 chains/s Finding the max performance is fun and interessting, but I think I have at least now found good parameters to use in different situations. I find my computer usable at 150 chains/s... I would be happy to contribute data to this project, and I guess I have not use for my GPU power more than maximum 5% of the time my computer is powered on. So, some questions again... In your last reply you say this: [Terje Sannum] >> My card is not overclocked, but can playing with these >> performance also give me wrong values? [Sascha Krissler] > yes. my gtx260 runs at 691 mhz. it is simple to compute test > values. use --work increment to use the same start values on > every run During all my testing the last days I have saved all the data generated. I have only tweaked the --device cuda:... and the --intermediate filter:runlength parameters. If my first test run with --chains 1024 is good, is the rest ok, or should I start all over? After two days I have saved 224Mb of data... -Terje On Thu, Aug 27, 2009 at 8:23 PM, Sascha Krissler <[email protected]>wrote: > 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? > > the current rate is an average rate so it approaches the current rate > in infinity (i.e. an hour). this will be fixed soon. > you could try --device cuda:threads=512 if your GPU has enough registers, > but last time i tried this, i got no improvement. > > > > > My card is not overclocked, but can playing with these performance > > parameters also give me wrong values? > > yes. my gtx260 runs at 691 mhz. it is simple to compute test values. > use > --work increment > to use the same start values on every run, then > with all other parameters the same, you should always get the same output. > This way you should be able to verify the correctness of the computation. > Write the data to a file or use > --consume print:results=X > where X is the number of chains you are generating, normally "print" only > displays > the first 16. > to fuel to competition, my GTX260 with 216 cores does 162.54 chains/s at > 691mhz, > but since it is headless i do not have to care for responsiveness. > > > > > 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... > > go ahead. > the whole purpose of the project is education. > (... and being in the newspapers :-) > also take a look at the CommandLine page in the trac which should clarify > some things. > ________________________________________________________________ > 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
