|
Title: Why do I solo/LAN-mine 25% slower than on a pool?? Post by: dragonmike on May 24, 2014, 09:21:18 PM Well it's all in the title.
I am solo-mining (or rather, pointing my mining rig onto my PC running the wallet in server mode) but each of my R9 280X is hashing at around 575Kh/sec instead of the usual 755 when I connect to any pool out there. Settings are the same. here's my wallet conf file: server=1 listen=1 gen=0 rpcuser=*** rpcpassword=*** rpcallowip=192.168.0.* rpcport=13932 Why is that so? Is anything wrong? Title: Re: Why do I solo/LAN-mine 25% slower than on a pool?? Post by: Remember remember the 5th of November on May 24, 2014, 09:59:51 PM The server shouldn't affect the speed of hashing, perhaps try increasing the queue size so that more work is queued and the miner doesn't stall.
Title: Re: Why do I solo/LAN-mine 25% slower than on a pool?? Post by: dragonmike on May 24, 2014, 10:39:19 PM it's very weird.
I have the feeling something is wrong with the setup of sgminer in the PimP distro. my conf file is identical to my other Pc (or the Bamt scrypt settings for that matter). The thing that makes me sceptical is one of the first lines displayed right after launch that says something along the lines of "unpatched BFI, nfactor 10, 1024..." Any idea? Title: Re: Why do I solo/LAN-mine 25% slower than on a pool?? Post by: Remember remember the 5th of November on May 24, 2014, 11:20:36 PM it's very weird. Yeah that might be a reason. BFI INT is an opcode that is used to speed up hashing, if it's not patched as it's apparent, it will use opcodes that perform slower.I have the feeling something is wrong with the setup of sgminer in the PimP distro. my conf file is identical to my other Pc (or the Bamt scrypt settings for that matter). The thing that makes me sceptical is one of the first lines displayed right after launch that says something along the lines of "unpatched BFI, nfactor 10, 1024..." Any idea? Title: Re: Why do I solo/LAN-mine 25% slower than on a pool?? Post by: dragonmike on May 25, 2014, 09:37:29 AM uhm... how do I patch it?
??? :P |