Bench problem

Comments

• dlehenky Member Posts: 2,249 ✭✭✭✭

  April 2016

  Usually it means you had some type of OpenCL error prior to actually launching the kernel. But it's Windows, so who knows? In your output, above, there's a bunch of garble printed before the hash rate lines, and I suspect there would have been an error message and code given, if it was readable.

  0 · Share on TwitterShare on Facebook
• w0lf Member Posts: 43 ✭

  April 2016

  thx dlehenky,is possible fix it?
  i see other guys this command work

  0 · Share on TwitterShare on Facebook
• o0ragman0o Member, Moderator Posts: 1,291 mod

  April 2016

  @w0lf try the warmup switch. The benchmark can be finished before the GPU has a chance to properly load the DAG.
  ethminer -G -M --benchmark-warmup 20

  0 · Share on TwitterShare on Facebook
• w0lf Member Posts: 43 ✭

  April 2016

  You are N1 this command finally work!
  unfortunately in mining I reach only half or less of the bench results with my 260x
  
  
  Bench screen : http://postimg.org/image/4bicgkwip/full/
  
  Mining screen: http://postimg.org/image/a62ca226v/
  
  thx

  0 · Share on TwitterShare on Facebook
• o0ragman0o Member, Moderator Posts: 1,291 mod

  April 2016

  OMG a 260x!? And it's killed the previous 4.59 benchamrk on my list !
  
  5.5Mhs, man that's even pushed it up a ranking from 38th worst to 37th!

  0 · Share on TwitterShare on Facebook
• w0lf Member Posts: 43 ✭

  April 2016

  hehe i know 260x is very bad,i'am selling it and buying some 7950.
  
  meanwhile I'm trying to understand why i reach this strange result with various linees with 0 H/s
  my command is :
  
  ethminer --farm-recheck 200 -G -F x.x.x.x:x --cl-local-work 256 --cl-global-work 16384
  
  
  
  this is the max result with 4 Mh/s

  Eth.jpg 103.6K

  0 · Share on TwitterShare on Facebook
• o0ragman0o Member, Moderator Posts: 1,291 mod

  April 2016 edited April 2016

  @w0lf You have global-work at 16384 which is taking ~800ms to work through so there's nothing to report in the 200ms farm recheck time. Drop global work down to 4096 and see how it compares. Don't know if it will make any practical difference.

  1 · Share on TwitterShare on Facebook
• w0lf Member Posts: 43 ✭

  April 2016

  ty o0ragman0o with global work 4096 i get 1 mH/s i think, but no lines with 0 h/s
  
  
  

  ethx2.jpg 168.4K

  0 · Share on TwitterShare on Facebook
• o0ragman0o Member, Moderator Posts: 1,291 mod

  April 2016

  @w0lf , no, you're getting 5Mh/s. The 1048576 figure is the actual number of hashes within the farm-recheck time of 200ms

  1 · Share on TwitterShare on Facebook
• w0lf Member Posts: 43 ✭

  April 2016

  Thanks o0ragman0o

  1 · Share on TwitterShare on Facebook