CCminer(SP-MOD) Modded GPU kernels.

[bensam1231]

I wouldn't use wood near any electronic equipment, unless the insurance agent is a friend of yours ;-)
(In event of fire, regardless how much care you took, the insurance will not pay if they know you used wood)

To each his own I guess but I'm absolutely confident the wood wouldn't make any difference that aluminum would in case of major failure.

Yeah I use wood too. Wood has a pretty high point of catching fire. It's a great insulator against electricity and heat up till that point.

Wood rack here too and no problems. Had 4x280x on it for almost a year before converting it to 6x 750ti, the 280x ran hot as hell and the wood barely got warm let alone hot enough to catch on fire. 750 ti obviously no problems, cool quit and efficent 

I'm pretty sure the concerns around wood are with regard to PC components failing catastrophically, not auto-ignition.  The auto-ignition point of white pine is like 400C...

Yeah, you're going to have other problems other then a wooden frame if you have an electrical fire. Silicon burns too as do the plastic most motherboards and heatsink fans are made out of.

This is why you invest in a good PSU that will auto shut off if such a thing happens. And second the smoke alarm.

[zTheWolfz]

Personally this rack is what I use and can be picked up at almost any hardware store. "Lowes/Homedepot"
I think could easily be modded for such a cause as these "even tho I haven't myself yet" but my needs where different at the time.
This unit: http://www.homedepot.com/p/Edsal-36-in-W-x-18-in-D-x-72-in-H-Steel-Commercial-Shelving-Unit-UR185L-BLK/202995256?MERCH=REC-_-NavPLPHorizontal1_rr-_-NA-_-202995256-_-N
which can be setup into two units one with 3 shelves the other will only have two shelves. Instead of one tall 5 shelve unit.
It splits in the middle and is part of the reason for odd number of shelves. The center shelve interlocks the two together.
In case you can't make that out in the store picture. But for under 60 bucks its a quick solution for muti card rigs or just rigs in general.
Open air and easy to keep cool. Could even easily set up a box fan on each end if heat becomes a problem. Push + Pull & enclose it with Plexiglas.

[chrysophylax]

i think its time to step up to a 980ti and have a look at how this thing works .. is it better? ...  and im not asking about the hashrate ...
#crysx

Looking at the BIOS of that card it has an absolute maximum of 366W power consumption limit if I'm reading it correctly which aligns perfectly with a techpowerup review.
Of course that's with some crazy synthetic test like FurMark and the usual peak consumption is about 300W. But even that is a lot.

I think these bigger cards are all about scaling; they get somewhat inefficient hash per watt at full speed but get pretty great if you decrease the power target like I found with the 970 a while back (https://bitcointalk.org/index.php?topic=1091755.msg11636995#msg11636995).
With downvolting it could be much more significant but I haven't tried it. So on one hand low profit margins warrants efficiency with lower power target but then the initial card price is too much but from another point of view if the profit margins were to increase in the future pushing the cards to hash as fast as they can would be more profitable. Also, different prices; in my case with the prices I'm presented with it doesn't worth it for me to go for anything above 970s.

Yup you can gain efficiency by lowering the TDP slider. However you lose hashrate and clockspeed doing it to the point where it's not even worth buying the bigger cards anymore. Running a 970 at 960 speeds is kinda pointless.

I wouldn't use wood near any electronic equipment, unless the insurance agent is a friend of yours ;-)
(In event of fire, regardless how much care you took, the insurance will not pay if they know you used wood)

To each his own I guess but I'm absolutely confident the wood wouldn't make any difference that aluminum would in case of major failure.

Yeah I use wood too. Wood has a pretty high point of catching fire. It's a great insulator against electricity and heat up till that point.

unless your cards throw out sparks ( like 7 of the gigabyte 7970 oc cards did ) when they decided to go faulty when i first started out ...

turns out they had a leak in the cooling fluid in the heat pipes and it was dripping onto the board - which shorted a few components and sparks started flying evrywhere - eventually killing the board ...

7 of them in a single batch with the same problem ...

wood maybe a good heat insulator - and bad conductor of eletricity - but there is no protection to raw sparks ...

wood? ... no tanx ...

#crysx

[chrysophylax]

Another binary:

- Faster lyra2v2 on gtx 750ti (+5%)
- Faster quark. (Pallas)
- Fixed crash in the whirlpoolx algo on linux(T Nelson)
- Other stability fixes by T Nelson.
- Fixed broken hash in cuda 7.0 (x11) (but cuda 7 is slower)

1.5.66(sp-MOD) is available here: (07-09-2015)

https://github.com/sp-hash/ccminer/releases/

The sourcecode is available here:

https://github.com/sp-hash/ccminer

will need to try this soon ...

#crysx

[Slava_K]

with git 1051 i have 28Mh on 2x980+1x960. git 1052 take not more then 23.8 Mh for me...

[sp_]

with git 1051 i have 28Mh on 2x980+1x960. git 1052 take not more then 23.8 Mh for me...

Is this lyra2v2? You need to find the correct intensity for your cards. Try -X 26 on the 980 and -X 16 on the 960'

And in the file cuda_lyra2v2.cu you can try different values for TPB52. It is set to 9. try all values from 1 to 32  compile test and keep the best one.

[Slava_K]

Yes, v2. Ok. -X works separately for cards (-X 10,9,8)?

[sp_]

yes

[sp_]

T Nelson are you there?

Seems to be an error in the latest builds, the miner won't exit without pressing ctrl+c

This was working fine in release 52

Code:

@ECHO OFF
TITLE -AUTO SWITCHING BACKGROUND GPU MINING-
:start

Miner\ccminer.exe -r 0 -a x11 -o stratum+tcp://ffpool.net:3533 -u X -p x11,x13,lyra2,neoscrypt,quark,qubit
Miner\ccminer.exe -r 0 -a x13 -o stratum+tcp://ffpool.net:3633 -u X -p x11,x13,lyra2,neoscrypt,quark,qubit
Miner\ccminer.exe -r 0 -a lyra2 -o stratum+tcp://ffpool.net:4433 -u X -p x11,x13,lyra2,neoscrypt,quark,qubit
Miner\ccminer.exe -r 0 -a neoscrypt -o stratum+tcp://ffpool.net:4233 -u X -p x11,x13,lyra2,neoscrypt,quark,qubit
Miner\ccminer.exe -r 0 -a quark -o stratum+tcp://ffpool.net:4033 -u X -p x11,x13,lyra2,neoscrypt,quark,qubit
Miner\ccminer.exe -r 0 -a qubit -o stratum+tcp://ffpool.net:4733 -u X -p x11,x13,lyra2,neoscrypt,quark,qubit

TIMEOUT /t 3
GOTO start

ccminer.exe -r 0 -i 11 -a x11 -o stratum+tcp://ffpool.net:3533 -u X -p x11,x13,lyra2,neoscrypt,quark,qubit
*** ccminer 1.5.65-git(SP-MOD) for nVidia GPUs by sp-hash@github ***
        Built with VC++ 2013 and nVidia CUDA SDK 6.5

  Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
   CUDA support by Christian Buchner, Christian H. and DJM34
  Includes optimizations implemented by sp , klaust, tpruvot,tsiv and pallas.

[2015-09-07 22:56:40] Intensity set to 11.0, 2048 cuda threads
[2015-09-07 22:56:41] Starting Stratum on stratum+tcp://ffpool.net:3533
[2015-09-07 22:56:41] NVAPI GPU monitoring enabled.
[2015-09-07 22:56:41] 1 miner thread started, using 'x11' algorithm.
[2015-09-07 22:56:41] Binding thread 0 to cpu 0 (mask 1)
[2015-09-07 22:56:41] Stratum subscribe answer id is not correct!
[2015-09-07 22:56:41] stratum_recv_line failed
[2015-09-07 22:56:41] ...terminating workio thread

And here it hangs and then the user have to click ctrl c to exit

[2015-09-07 22:58:16] CTRL_C_EVENT received, exiting once miner jobs complete.  Ctrl+C again to abort miner jobs

[t-nelson]

T Nelson are you there?

Seems to be an error in the latest builds, the miner won't exit without pressing ctrl+c

This was working fine in release 52

-- SNIP --

And here it hangs and then the user have to click ctrl c to exit

[2015-09-07 22:58:16] CTRL_C_EVENT received, exiting once miner jobs complete.  Ctrl+C again to abort miner jobs

Must be Windows only.  Linux seems fine.  Can you grab me a stack trace with it hung?  I won't be able to check Windows for several hours.

[t-nelson]

T Nelson are you there?

Seems to be an error in the latest builds, the miner won't exit without pressing ctrl+c

This was working fine in release 52

-- SNIP --

And here it hangs and then the user have to click ctrl c to exit

[2015-09-07 22:58:16] CTRL_C_EVENT received, exiting once miner jobs complete.  Ctrl+C again to abort miner jobs

Must be Windows only.  Linux seems fine.  Can you grab me a stack trace with it hung?  I won't be able to check Windows for several hours.

Scratch that.  I botched the rebase to HEAD.  Gimme a few to rerecompile.

[t-nelson]

T Nelson are you there?

Seems to be an error in the latest builds, the miner won't exit without pressing ctrl+c

This was working fine in release 52

-- SNIP --

And here it hangs and then the user have to click ctrl c to exit

[2015-09-07 22:58:16] CTRL_C_EVENT received, exiting once miner jobs complete.  Ctrl+C again to abort miner jobs

Must be Windows only.  Linux seems fine.  Can you grab me a stack trace with it hung?  I won't be able to check Windows for several hours.

Scratch that.  I botched the rebase to HEAD.  Gimme a few to rerecompile.

https://github.com/sp-hash/ccminer/pull/44

[sp_]

thanks.

[tbearhere]

I am running all my stuff in alu frames. These +five more where stacked with 5 x 280x cards until two years ago when i stopped mining. I have a total of ten frames but i think i will stop when these are filled up because i promised myself to not go full retard again

In total there will be 20 x 750Ti and 5 x 280x cards.

I went with metal frame this time instead of wood. Building from scratch.   What are the cost of those frames plz. thz
Sorry sp for messing your thread up.

[jpouza]

I am running all my stuff in alu frames. These +five more where stacked with 5 x 280x cards until two years ago when i stopped mining. I have a total of ten frames but i think i will stop when these are filled up because i promised myself to not go full retard again

In total there will be 20 x 750Ti and 5 x 280x cards.

hahah full retard mode was funny
Nice stands, very clean setups.

Cheers

[pallas]

What's the most accurate way to benchmark kernel modifications?
Using --benchmark or connecting to a pool? What time interval? Any other reccomendation?

[myagui]

Most important recommendation I have, is to benchmark at a low'ish & fixed GPU clock setting (stuck in performance mode), along with a high'ish & fixed fan speed. This should eliminate most/all thermal & clock stability variations.

For significant code changes, and particularly when the changes are not strictly related to the hashing algorithm in particular - so more about backend/generally efficiency - definitely need to test with a pool, Nicehash is usually great at that, with a minimum interval of 4 hours, but ideally, a full 24 hour cycle.

For specific kernel changes, benchmark should be best (and also the practical approach). I tend to benchmark for whatever duration is necessary until I see that I get about 5 minutes of stable output speed & stable temperature reading. Some algorithms take a while ramping up, others not so much, some algorithms start faster, but slow down once temperatures get high enough.

[bathrobehero]

What's the most accurate way to benchmark kernel modifications?
Using --benchmark or connecting to a pool? What time interval? Any other reccomendation?

Poolmining is never completely reliable, especially if there's vardiff which will always fluctuate. But even with fixed diff you'll have to run it for a long time to be sure.
--benchmark had plenty of issues in the past so I've stopped using it so I'm not sure how it is recently.

For checking speed only, I personally like to just solomine to any local wallet, doesn't even matter if the algo is different and just check the reported hashrate.
Stable clocks and fix fanspeed recommended.

Regarding aluminum cases, I'm also curious how much people who own them paid for them.

[chrysophylax]

What's the most accurate way to benchmark kernel modifications?
Using --benchmark or connecting to a pool? What time interval? Any other reccomendation?

Poolmining is never completely reliable, especially if there's vardiff which will always fluctuate. But even with fixed diff you'll have to run it for a long time to be sure.
--benchmark had plenty of issues in the past so I've stopped using it so I'm not sure how it is recently.

For checking speed only, I personally like to just solomine to any local wallet, doesn't even matter if the algo is different and just check the reported hashrate.
Stable clocks and fix fanspeed recommended.

Regarding aluminum cases, I'm also curious how much people who own them paid for them.

frames? ... i build them custom ...

the frame ( 1.5mm square aluminium tubing ) - edge connectors - screws and lugs - angle iron ( 90 degree edging ) ... all this comes to approx $70.00aud ...

but initially i had to buy the cutting and measuring equipment as well as the files and mallets ( yes plastic head mallets - not hammers ) ...

parts alone - not counting labour - if you are looking at adding teh countless hours to design the thing in the first place ...

prototype 1 - prototype 2 and now prototype 3 is probably the design we are going with ...

hope that helps bathrobehero ...

#crysx

[pallas]

I must say that I didn't have any problem benchmarking amd cards: if the room was hot, I'd put the fans at high speed, run the miner and wait a couple minute to stabilize, and that's it. I could make 100 changes to a kernel in a day and check them all, accurately.

On nvidia I have throttling problems I can't easily fix (the cards reduce clock speed in a number of situations I just can't predict), overclocking/downclocking is more difficult as the cards tend to change clocks by themselves, and the hashrates fluctuates wildly, and even changes between ccminer runs.
The rig is headless so I only have nvidia-smi to work with, and it can't set the fan speed.
So when I make a little kernel speedup, I spend more time benchmarking it (to be sure it's indeed an improvement), than making the improvement itself :-/
Maybe there are some nvidia-smi settings to make it more stable?
Or maybe on windows it's different...
Finally I may need a workstation with a nvidia as main card, and work on it.