Big dog could just easily pretend he's 35 different persons all mining at 1% of the net hashrate to avoid the 'tax'.
|
|
|
now usb risers all the way - 56 of them and growing - and not one hitch - with less power issues and almost NO burnouts of cables or connectors ... (...) #crysx
You've got one of the biggest private NVIDA farms in the world. The most famous australian that I can think of on a friday night is the Australian comedian Jim Jefferies. https://www.youtube.com/watch?v=W3tM5UvvKKECheers mate Jim Jefferies is hilarious. He's one of my favourites along with Louis CK, Doug Stanhope, Jimmy Carr and Lewis Black.
|
|
|
We're going to take your advice and make it 1 minute blocks, thanks for the input Crest.
Just to confirm what has been said, 1 minute or even 30 seconds is fine (Cypher, Droidz works fine with it) but below that it will probably cause issues (forks). And of course with higher block frequency the blockchain is going to get that much bigger in time so the wallet will use that much more space and will take more time to sync for future users.
|
|
|
Was it a Ribbon or USB cable riser?
On Topic, the 1.5.48 build on my single 750 TI card gets between 5866 to 7200 KH/s Quark using the -i 22 -g 5 usually closer to 6300. However, I see a drop on my 6 750 ti card unit running at 36600 vs 37083 on build 1.5.47 commit 749. I have gone back to using the 1.5.47 commit 749 for it, with no extra parameters it is getting 37150 kh/s on screen and seems like it is getting more consistently on westhash (36.6 to 44.3MH/s). Windows 8.1 Pro no OC or bios flash EVGA SC cards.
USB riser, open rig.
|
|
|
bathrobehero,
What is the advantage for mining when increasing the TDP of a 750Ti via a flashed BIOS?
I imagine that it allows a higher overclock and therefore higher hashrate. But, I have had a PNY 750Ti OC for over a year, and I never flashed it. I never saw anyone posting any hashrates for algorithms that I cared to mine that were significantly higher than what my card would do (with my particular card's stock BIOS - OC maximized). Sure, maybe a less than 5% faster hashrate than my card, but that just didn't seem worth the risk and effort.
Am I correct or mistaken?
It's both higher overclock and more stability with overclocks. Even though I'll never get how some people can overclock their 750 Ti cards to ~1500 mhz and be stable, with increased TDP I could overclock to around 1350-1380 mhz and still have the rig running for weeks without crashing (for most algorithms that is). I always ready to jump onto new coins and solomine as much as I can until the pools join and the difficulty shoots up so I appreciate higher hashrate over hashrate/power consumption figures. Just replace the bios with the gforce black bios. Same cooler, same power setting, more hash
Never heard of it but I don't think that is any different from a TDP mod. I just think the voltage regulation modules on these particular cards are just not equipped to handle anything over stock figures for long periods of time.
|
|
|
Offtopic: Just as a reminder for people with TDP modded Gigabyte 750 Ti OC (GV-N75TOC-2GI) cards; expect your cards to die. Out of 6, now 2 of them died on me in 11 months (no fan, no screen, nothing). And I 'only' increased the TDP to 45W (instead of the usual 60W) and only after 3-4 months of stock use. I usually had +140 to +170 mhz on the core with stock mem clocks. Temps were always around 60°C with the max temp target set to 65°C. I read about others with similar issues a couple of times. An old post but this was close by: blahij May 11th, 2014 at 03:08 I had 6 flashed hashing @ 300kh for a month or two. Had two burn themselves out day before and then another the next day. Temps were fine and I can see some discoloring on the back and one component looks blown-out? Mine were Gigbyte and I used the posted BIOS on this site. Quote from http://cryptomining-blog.com/1014-how-to-increase-the-geforce-gtx-750-ti-power-target-limit/
|
|
|
Price 300 sathoshi. We're going to zero
now what?
Main problem is that noone want to buy. Sad bu true.
Of course nobody wants to buy if it isn't on any reputable exhange yet. C-cex vote, really? When was the last time a coin went through a vote and was successful? I mean you can get onto c-cex just by hosting an ico there... If this coin won't get added to c-cex or bittrex real soon this will be dead. It might already be too late.
|
|
|
:loop ccminer.exe -r 1 -R 5 -a quark -o stratum+tcp://us-west01.miningrigrentals.com:3333 -u me -p x -d 0,1,2 taskkill -t -f /im ccminer* timeout -t 1 ccminer.exe -r 1 -R 5 -a quark -o stratum+tcp://us-central01.miningrigrentals.com:3333 -u me -p x -d 0,1,2 goto loop
Should prevent the crash.
Thanks bathrobehero. But it was crashing at the goto loop. And said at that point it couldn't find ccminer .. Yes, I misunderstood the problem. I couldn't replicate it though.
|
|
|
I'm sticking with Spotify.
|
|
|
what do we call the .conf
premine.conf
|
|
|
I'm out even before joinning.
|
|
|
TASKKILL--
I inserted your taskkill lines of code between every launch line in the Windows batch file for Yaamp. I still get Windows error reports, not every time, but enough to render the batch file useless for a long-running script. Maybe I haven't completely shutdown the error reports in my system. I haven't compiled ccminer with your suggested correction. I need to set up a Windows build toolchain...
--scryptr
So it sometimes crashes for you. In that case I doubt the code change will help you. The batch file doesn't call ctrl+c on its own. ERROR REPORTING-- I redid my Error Reporting configuration in Win 7 x64. I selected "ccminer.exe" as a program to specifically be ignored. I saved this as an administrator. I still get "ccminer.exe has stopped working" between every few algo changes in the Yaamp batch file. If there is another way to shut the error reporting off, I haven't found it yet. --scryptr If I remember correctly I used a reg key like this (Option two): http://www.sevenforums.com/tutorials/194181-windows-error-reporting-disable-windows.html
|
|
|
TASKKILL--
I inserted your taskkill lines of code between every launch line in the Windows batch file for Yaamp. I still get Windows error reports, not every time, but enough to render the batch file useless for a long-running script. Maybe I haven't completely shutdown the error reports in my system. I haven't compiled ccminer with your suggested correction. I need to set up a Windows build toolchain...
--scryptr
So it sometimes crashes for you. In that case I doubt the code change will help you. The batch file doesn't call ctrl+c on its own.
|
|
|
Further, the Windows batch command "taskkill" will not find the imagename "ccminer*" if a user closes the "ccminer.exe" with a "control-c" keystroke, because ccminer has abruptly been closed. This abrupt closing triggers a Windows error response frequently, and disrupts the loop on the ccminer launch batch file. If running ccminer in a round-robin batch file, the Windows error response prevents ccminer from reconnecting and mining until a manual intervention occurs.
Closing out of ccminer.exe in a clean fashion under Windows may require some changes to the source code of ccminer itself.
--scryptr
I have the windows error reporting completely disabled on my rigs so crashing apps just silently close without throwing error messages. But I've just tested it on my main rig and it crashes due to this line: https://github.com/sp-hash/ccminer/blob/windows/ccminer.cpp#L2383That proper_exit(0); is not so proper I guess. Replacing it simply to exit(0); prevents the crash when you use ctrl+c. It asks if you want to termiate the batch file and pressing N let it continue. And if taskkill doesn't find it's target it doesn't do anything. ROUND-ROBIN-- Yaamp adapted the round-robin switch to rotate between the highest-paying algo, and it works until Windows kicks out that error. I was experimenting with a simple batch file that calls a JSON.conf file. I'll work your code into my Yaamp round-robin file and see if it will run well. I suppose that means I will have to compile under Windows. If I get that far, maybe it will rotate for me. I did try to disable all the Windows error-reporting. --scryptr The error I described should only happen if you use ctrl+c. I don't use yaamp but as I see it they only let you connect to their highest paying algo and disconnect you if you try to connect with any other algo. With -r 0 ccminer won't reconnect so it just closes cleanly then the next line of the batch file gets executed. I've tried the yaamp example loop and it's working flawlessly. So now I'm completely confused as to what is the problem with the loop.
|
|
|
X11- meh. Too many farms.
Sad but very true.
|
|
|
 { "blocks" : 83, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : { "proof-of-work" : 2.53166360, "proof-of-stake" : 0.00024414, "search-interval" : 0 }, "blockvalue" : 40000000000, "netmhashps" : 2.20109562, "netstakeweight" : 0.00000000, "errors" : "", "pooledtx" : 0, "stakeweight" : { "minimum" : 0, "maximum" : 0, "combined" : 0 }, "stakeinterest" : 1000000, "testnet" : false }
|
|
|
Further, the Windows batch command "taskkill" will not find the imagename "ccminer*" if a user closes the "ccminer.exe" with a "control-c" keystroke, because ccminer has abruptly been closed. This abrupt closing triggers a Windows error response frequently, and disrupts the loop on the ccminer launch batch file. If running ccminer in a round-robin batch file, the Windows error response prevents ccminer from reconnecting and mining until a manual intervention occurs.
Closing out of ccminer.exe in a clean fashion under Windows may require some changes to the source code of ccminer itself.
--scryptr
I have the windows error reporting completely disabled on my rigs so crashing apps just silently close without throwing error messages. But I've just tested it on my main rig and it crashes due to this line: https://github.com/sp-hash/ccminer/blob/windows/ccminer.cpp#L2383That proper_exit(0); is not so proper I guess. Replacing it simply to exit(0); prevents the crash when you use ctrl+c. It asks if you want to termiate the batch file and pressing N let it continue. And if taskkill doesn't find it's target it doesn't do anything.
|
|
|
To many blocks with 0 rewards , not nice About 16 hours worth. Then another 16 hours with very low reward. I'm curious how this will work out though.
|
|
|
|