CCminer(SP-MOD) Modded GPU kernels.

[sp_]

Hey, what are Your OC values, and what cards are You using?

Factory clocks, different cards. Mostly without the 6pin power connector.

[1714687086]

1714687086

[1714687086]

1714687086

[blue-yu]

Hey, what are Your OC values, and what cards are You using?

Factory clocks, different cards. Mostly without the 6pin power connector.

These are great results for quark - i think. I am getting 6600-6800 with my gigabyte 750ti with OC +150cpu +300mem. I see one of Your gpu is doing 8600! Other are 7900, 7700,...

What am I doing wrong?

[sp_]

Hey, what are Your OC values, and what cards are You using?

Factory clocks, different cards. Mostly without the 6pin power connector.

These are great results for quark - i think. I am getting 6600-6800 with my gigabyte 750ti with OC +150cpu +300mem. I see one of Your gpu is doing 8600! Other are 7900, 7700,...
What am I doing wrong?

Private kernal

Average for 6 cards is around 7MHASH on the 750ti. The opensource version does around 5.9MHASH. (factory clocks)

[blue-yu]

Hey, what are Your OC values, and what cards are You using?

Factory clocks, different cards. Mostly without the 6pin power connector.

These are great results for quark - i think. I am getting 6600-6800 with my gigabyte 750ti with OC +150cpu +300mem. I see one of Your gpu is doing 8600! Other are 7900, 7700,...
What am I doing wrong?

Private kernal

Average for 6 cards is around 7MHASH on the 750ti. The opensource version does around 5.9MHASH. (factory clocks)

Aaaa, that is the trick. How much btc is that top secret project

[zjy]

Hey, what are Your OC values, and what cards are You using?

Factory clocks, different cards. Mostly without the 6pin power connector.

These are great results for quark - i think. I am getting 6600-6800 with my gigabyte 750ti with OC +150cpu +300mem. I see one of Your gpu is doing 8600! Other are 7900, 7700,...
What am I doing wrong?

Private kernal

Average for 6 cards is around 7MHASH on the 750ti. The opensource version does around 5.9MHASH. (factory clocks)

7M Also have no money to earn

[zjy]

Hey, what are Your OC values, and what cards are You using?

Factory clocks, different cards. Mostly without the 6pin power connector.

These are great results for quark - i think. I am getting 6600-6800 with my gigabyte 750ti with OC +150cpu +300mem. I see one of Your gpu is doing 8600! Other are 7900, 7700,...
What am I doing wrong?

Private kernal

Average for 6 cards is around 7MHASH on the 750ti. The opensource version does around 5.9MHASH. (factory clocks)

we need axion GPU miner 

[bensam1231]

What are you mining to get a 6-12 month ROI?!?! Oo
Mining Quark for instance right now, at $.1144 KwH for a 970 nets $.32 per day after power. That ROI in about 1000 days, or three~ years. Back before SAK crashed, it was about 8-12 months for ROI.
Edit: Release .57 is broken for Neoscrypt. One of my machines (W8) it doesn't do anything and hangs when it connects to the pool, my other machine (W10) only one of the 970s works even though it tries to start all three of them.

Cost of power: $0,06KWH
Cost of a used board (750ti) $100
Average outside temp in the summer. 10C (I live close to the north pole)
Private kernals +30%

Private kernel and cheap power. -_-

[sp_]

Not for sale. But you can keep donating, so I can publish small increases in the hashrates for free.

Next up is another groestlcoin optimalization.

From 23,7 to 24 MHASH on the gtx 970 windoforce oc.(stock) (will submitt later tonight)

The speed on AMD cards with the pallas opensource is:

v1 - to be compiled with catalyst 14.6 or 14.7:

R9 290x @1125 Mhz: ~26.4 Mh/s
R9 290 @1200: ~25 Mh/s
R9 280x (stock): ~18 Mh/s
7950 @1200: ~16 Mh/s
R9 270X: ~9.7 Mh/s

v2 - experimental hawaii only bin:

R9 290x @1125 Mhz: ~34.4 Mh/s
R9 290 @1100: ~30.6 Mh/s

[chrysophylax]

I was thinking of a hybrid miner when I noticed how well cpuminer-multi hashed lyra2. If the best performing
cpu sub-algo could be offloaded from the gpu, the gpu could work more on the other sub-algos. Even if the offloaded
sub-algo is slower on a cpu wouldn't the parallelization result in a higher overall hash rate?

The problem is the pci-e bandwidth. Moving buffers through 1x pcie will slow.. I was thinking let the cpu work in parallell to find hashes togeter with the gpu.
The cpu code is already written... But perhaps bether to just run 2 miners. one for the cpu and one for the gpu..

i do that currently ... cpu - axiom ... gpu - x11 ...

separately in to different consoles under fedora ( amd and nvidia ) ...

but a 'hybrid' miner that runs both cpu and gpu with the one miner - that would be interesting ...

#crysx

[chrysophylax]

With the latest commit, I get on Quark 38142 Kh/s on my 6 card EVGA 750 Ti SC with no OC, No Bios change Windows 8.1 Pro (6357 per card).   If I put the fans to 100% I can get about 15 Kh/s more per card.  

X11 19070 Kh/s Rig / 3178.33 Kh/s per card  (Note this is with any -g or -i parameter)

thats the great thing about this fork - sp puts the intensity levels ( -i ) as high as he can as default in the code so that the miner works at peak speed ...

this can backfire with some cards - as the intensity levels are a little too high at default - but usually works quite well overall ...

for those who want to mine as a donation for sp's work - i will be working on getting the donation links running and active today ...

a few more issues to be rid of and the servers ( with donation links ) will be ready to mine with ...

will notify here - https://bitcointalk.org/index.php?topic=1089744 ...

#crysx

Yeah... there is very little configuration for this miner compared to SG. You just plug in pool and algo information and that's it.

That also means people aren't rewarded for tweaking the miner in addition to setting it up, but you know. That's just the elitist miner in me talking.

sp is working on oc setting tuning within the miner though ...

its just limited by the nvidia toolkit and from nvidia themselves ...

eg - memclock and gpuclock is possible under linux using nvidia-smi - BUT - nvidia themselves are limiting availability to the cards that can be oc'd to those that are the 'elite' upper range cards ... my gigabyte 750ti oc lp card is not on that list ...

so when there is more flexibility to do that - i am sure there will be the switches / parameters that will be built into ccminer ( if it is still called that of course ) that will allow easy oc - like that in sgminer ...

i really do like the sgminer 'stats-candy' ...

one can see all that one needs - in one screen ... except for the current block number ( not just the hash ) ... unlike the rolling list that ccminer has ...

for the layman and lazy miner - this is a good thing ... for tweakers and power users / miners - this is a little lame ... but works ...

#crysx

Tpruv's windows version does allow setting gpu clock on the command line.   This is a feature I'd like to see in SP's mods.
 
fyi: I was Angora but lost that account as pw got changed and could not get the reset email.

i recognize angora ...

message mprep with all the details that you can to prove that was your account - and he will ( eventually ) get to it ...

at least - thats what happened to a hacked account on here earlier ...

as for tpruvots version - it is a nice version to use ... but i am unsure of the actual commandline settings ( and whether they work or not ) and how to activate the settings for the gigabyte 750ti oc lp cards ...

even though tpruvots fork is not as optimized as sps - i would really like to know how to oc via command line using his fork of ccminer and test how effective it is ...

#crysx

[chrysophylax]

Tpruv's windows version does allow setting gpu clock on the command line.   This is a feature I'd like to see in SP's mods.
 fyi: I was Angora but lost that account as pw got changed and could not get the reset email.

You can also set the gpu clock in my fork. Windows only.(use the latest drivers) Setting the clock will only work on the highend cards. gtx 970/980 etc.

the settings are called:

--gpu-engine and gpu-memspeed

yup - thats what i was looking for ...

tanx sp ...

just reinforced the fact that nvidia are not prepared to release a driver version that allows full oc capabilities on the 'lower' end cards like 750ti ...

#crysx

[pallas]

Not for sale. But you can keep donating, so I can publish small increases in the hashrates for free.

Next up is another groestlcoin optimalization.

From 23,7 to 24 MHASH on the gtx 970 windoforce oc.(stock) (will submitt later tonight)

The speed on AMD cards with the pallas opensource is:

v1 - to be compiled with catalyst 14.6 or 14.7:

R9 290x @1125 Mhz: ~26.4 Mh/s
R9 290 @1200: ~25 Mh/s
R9 280x (stock): ~18 Mh/s
7950 @1200: ~16 Mh/s
R9 270X: ~9.7 Mh/s

v2 - experimental hawaii only bin:

R9 290x @1125 Mhz: ~34.4 Mh/s
R9 290 @1100: ~30.6 Mh/s

Mine is faster on Tahiti - bin is public.

that falls into the "v2" category ;-)
in order to avoid confusion, I might link your tahiti bin in the OP and add its hashrate to that list.
are you ok with that?

[Vita1ico]

I'm on the GTX 960 in the hash algorithm x11 5400 kH/s. It is little or normal?

[Epsylon3]

Tpruv's windows version does allow setting gpu clock on the command line.   This is a feature I'd like to see in SP's mods.
 
fyi: I was Angora but lost that account as pw got changed and could not get the reset email.

These clock and power limit flags only works for x64 builds on windows and for linux (require nvml.dll which doesnt exists for 32 bit binaries)

sp just call the nvidia-smi, but mine is more complex, i check first the possible values and set them according to possible values. But about these clocks, it just a limit, not an overclock... same with sp version... The plimit works (i even exploded a PSU with that)

[chrysophylax]

Tpruv's windows version does allow setting gpu clock on the command line.   This is a feature I'd like to see in SP's mods.
 
fyi: I was Angora but lost that account as pw got changed and could not get the reset email.

These clock and power limit flags only works for x64 builds on windows and for linux (require nvml.dll which doesnt exists for 32 bit binaries)

sp just call the nvidia-smi, but mine is more complex, i check first the possible values and set them according to possible values. But about these clocks, it just a limit, not an overclock... same with sp version... The plimit works (i even exploded a PSU with that)

so so you have instructions on how to use these settings? ...

what the commanline parameters are - how to implement them on the commandline - what limits you can have ...

im curious as to how to get all this running in fedora 20 x64 - cuda 6.5 ...

empsylon3 - maybe you can answer this ... i have upgraded one of the systems to fedora 21 x64 and cuda 7.0 ... compiled both sps fork and tpruvots fork and both are giving cpu validation errors on the two algos that i tested - x11 and quark ...

what could this be? ... and how do i fix it? ...

tanx ...

#crysx

[sp_]

My fork only works with cuda 6.5 or 7.5.

Cuda 7.5beta shows a drop in hashrate of around 30% in the x11 algorithm but it validates. A 750ti is down from 3MHASH to 1.9

[sp_]

These clock and power limit flags only works for x64 builds on windows and for linux (require nvml.dll which doesnt exists for 32 bit binaries)
sp just call the nvidia-smi, but mine is more complex, i check first the possible values and set them according to possible values. But about these clocks, it just a limit, not an overclock... same with sp version... The plimit works (i even exploded a PSU with that)

NVIDIA has removed support for x86 in their API, so I just call their command line tool. Seems to work to change the clocks on the gtx970/980 if you know the valid clocks. 750ti is not supported.

[chrysophylax]

These clock and power limit flags only works for x64 builds on windows and for linux (require nvml.dll which doesnt exists for 32 bit binaries)
sp just call the nvidia-smi, but mine is more complex, i check first the possible values and set them according to possible values. But about these clocks, it just a limit, not an overclock... same with sp version... The plimit works (i even exploded a PSU with that)

NVIDIA has removed support for x86 in their API, so I just call their command line tool. Seems to work to change the clocks on the gtx970/980 if you know the valid clocks. 750ti is not supported.

tanx sp ...

#crysx

[chrysophylax]

My fork only works with cuda 6.5 or 7.5.

Cuda 7.5beta shows a drop in hashrate of around 30% in the x11 algorithm but it validates. A 750ti is down from 3MHASH to 1.9

ok - so cuda 7.0 is really a dead way to go ...

i wonder if im better to downgrade back and get the test machine runnign under 6.5 again ... this will take some work and time - but better to go back to a working system than a step forward with less has ...

i think waiting for cuda 7.5 to be running mainstream is probably the better way to go ...

tanx again sp ...

#crysx

[joblo]

My fork only works with cuda 6.5 or 7.5.

Cuda 7.5beta shows a drop in hashrate of around 30% in the x11 algorithm but it validates. A 750ti is down from 3MHASH to 1.9

ok - so cuda 7.0 is really a dead way to go ...

i wonder if im better to downgrade back and get the test machine runnign under 6.5 again ... this will take some work and time - but better to go back to a working system than a step forward with less has ...

i think waiting for cuda 7.5 to be running mainstream is probably the better way to go ...

tanx again sp ...

#crysx

Problem is cuda 6.5 isn't supported on newer Linux releases. The latest supported Fedora is 20
which EOLed a month ago.

Seems odd that Nvidia would drop cuda 6.5 if cuda 7 was performing poorly.