CCminer(SP-MOD) Modded GPU kernels.

[jjjordan]

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?

Yeah, go ahead; just credit me.

I was looking around about mining groestl and it's only groestlcoin, right?
Only one exchange without volume, so bag holding only?

[1714662354]

1714662354

[1714662354]

1714662354

[1714662354]

1714662354

[1714662354]

1714662354

[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?

Yeah, go ahead; just credit me.

I was looking around about mining groestl and it's only groestlcoin, right?
Only one exchange without volume, so bag holding only?

you can mine diamond as well.

[lawrencelyl]

Pretty nice increase in hashrate for Axiom with latest cpu miner:

[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

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.

i agree - it does seem odd ...

unless they have something up their sleeve that they are about to release - then i would have summized that the future releases would not only be backward compatible but also at the same level of competency for compilations ...

instead - its worse hashrates - even worse compilation issues - and a 7.5 rc that gets release very shortly after the 7.0 release ... only to push fedora cuda repos forward without backward compatibility ...

its just downright silly ...

ill be reinstalling fedora 20 x64 with cuda 6.5 on the test machine again ... tomorrow or the next day ...

nite all ...

#crysx

[bathrobehero]

They probably don't care about mining and rendering and other CUDA calculations might even improved.

[jjjordan]

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?

Yeah, go ahead; just credit me.

I was looking around about mining groestl and it's only groestlcoin, right?
Only one exchange without volume, so bag holding only?

you can mine diamond as well.

I see, that makes more sense... Was just wondering why you guys are optimizing groestl if it's not that popular...

[chrysophylax]

They probably don't care about mining and rendering and other CUDA calculations might even improved.

the funny thing is - they originally built cuda to spearhead the 'render farm' movie niche and scientific market that was wide open a little while ago ...

why would they screw things up now? ...

you are probably right though - they dont care about mining and the rest of the community :| ...

#crysx

[bathrobehero]

They probably don't care about mining and rendering and other CUDA calculations might even improved.

the funny thing is - they originally built cuda to spearhead the 'render farm' movie niche and scientific market that was wide open a little while ago ...

why would they screw things up now? ...

you are probably right though - they dont care about mining and the rest of the community :| ...

#crysx

We should probably make them more aware of the mining community.

To add to my previous comment:

[Epsylon3]

you dont have to use the distribution packages to use cuda... all the versions can be used (and even mixed on linux) for a project.

I repeat it again... there was an improvement in the 7.5 RC (over the 7.0 ) and a big part of the speed reduction is related to the fine tuning which should be redone due to the different register count in the output "binaries". Kernels which were "oppressed" (with a low limit compared to the required count of registers) are slower

[flipclip]

I see, that makes more sense... Was just wondering why you guys are optimizing groestl if it's not that popular...

Groestl is used in quark (possibly others), so faster Groestl means faster quark.

[pallas]

I see, that makes more sense... Was just wondering why you guys are optimizing groestl if it's not that popular...

Groestl is used in quark (possibly others), so faster Groestl means faster quark.

and x11 and x13 and lyra2 etc....
but, the code is only shared at times, so it takes work to spread to all the algos.

[joblo]

you dont have to use the distribution packages to use cuda... all the versions can be used (and even mixed on linux) for a project.

I repeat it again... there was an improvement in the 7.5 RC (over the 7.0 ) and a big part of the speed reduction is related to the fine tuning which should be redone due to the different register count in the output "binaries". Kernels which were "oppressed" (with a low limit compared to the required count of registers) are slower

There are two issues here and I don't know which one you are responding to.

Yes multiple versions of cuda can be used on the same Linux installation, just need to specify
--with-cuda when running ./configure. The RPM repo supports this as well with seperate meta-packages
for cuda 6.5 and 7.

Given that cuda 6.5 is still the best for mining at this time the other issue is finding a Linux distro that
has 6.5 available from Nvidia, either in the distro's package format or run file. The last 6.5 for Ubuntu was
14.04, for Fedora it was 20.

I know that in Fedora some RPMs for release n will work in release n+1. In fact the Fedora 18 version of
Virtualbox was carried over all the way to 21. it's only in Fedora 22 that VBox created a new release version.

I don't know if this is the case with cuda but it might be worth a try.

[pallas]

There is something wrong with the dependencies of groestl_functions_quad.cu: modifying it doesn't trigger recompile of the files that include it, like groestlcoin.cu

[sp_]

they are exluded to speedup the build. If you save the file in the editor, they will recompile.

1>------ Build started: Project: ccminer, Configuration: Release Win32 ------
1>  Skipping CUDA source file bitslice_transformations_quad.cu (excluded from build).
1>  Skipping CUDA source file groestl_functions_quad.cu (excluded from build).
1>  Compiling CUDA source file quark\cuda_quark_compactionTest.cu...

[pallas]

That's not how a Makefile is supposed to work.
When I modify a file, the files that include it should be recompiled on the next build.
Otherwise you need to find all that files and touch them manually. And if you don't remember to do it, the changes will not be reflected in the binary.

[hashbrown9000]

@chrysophylax , if you'd like i could try to upload an image to Mega when I had an HDD installation with overclocking working on the 750ti's. It's Ubuntu 14.04 with CUDA 6.5 and 346.xx nvidia drivers.  The thing was very stable and I have the HDD saved for a backup in case one of my USB sticks goes down.

[chrysophylax]

@chrysophylax , if you'd like i could try to upload an image to Mega when I had an HDD installation with overclocking working on the 750ti's. It's Ubuntu 14.04 with CUDA 6.5 and 346.xx nvidia drivers.  The thing was very stable and I have the HDD saved for a backup in case one of my USB sticks goes down.

tanx hashbrown9000,

that would be great ... is it a usb stick install? ...

im not familiar with debian based distros - though i have tinkered with them ...

im more a rhel based ( rhel - fedora ) user and admin guy ...

but i would really like that - yes ... please share ...

i have a great deal of running around to do today - so ill pop in when time permits ...

tanx ...

#crysx

[bathrobehero]

Bit off topic but in GPU-Z there's an ASIC quality estimation tool and I checked all of my GPUs and it seems there is a correlation between the estimated quality and overclocking capabilities.

It apparently takes into account the voltage requires to operate and some other factors to generate a number that doesn't change with overclock or anything.
Higher ASIC quality cards require less voltage to operate and they also naturally boost higher and can take the most OC without overvolting.

So I started incrementally overclocking all cards in a rig with 6 x Asus non-6-pin cards which had a wide spectrum of ASIC quality (62.7% 69.4% 70.6% 70.7% 72% 80.6%) and sure enough the highest quality was the last to crash by a large margin.
Here's a picture showing how to check it. (source)

My highest card is a Gigabyte GTX 750 Ti Windforce with 83.8% and my lowest is my main card I'm not mining with but kept for the occasional gaming with 66.6% which is a 780 Ti and it overclocks absolutely terribly. The average of all my cards is 75%.


So ideally cards should be overclocked based on these figures for maximizing efficiency and stability.
High quality high end cards might even have a decent value for enthusiast gamers.

[AliMan]

I gotta say, I'm not a believer in that ASIC thing, that just seems to be a bunch of horse.

I've had lower and higher ASIC cards, both OC quite well, and also the higher hasn't always been the best. Basically, most of these cards OC till a certain limit, regardless of how well they're made.

From what I've seen, extremely bad cards can't even hold their factory boost clock, but then again, it's got nothing to do with ASIC.

[pallas]

I wanted to try cuda 7.5 and here's my experience with it and neoscrypt mining.

On cuda 6.5 I'm working on an optimized version which does about 560 Mh/s on 970.
Simply switching to cuda 7.5 brought it down to 420.
So I wanted to try to reach at least the same hashrate as before, but I failed: after tuning it for the new cuda version for half a day, I was only able to bring it up to about 460.

Any suggestion on how to do better than that? Or should I just leave 7.5 alone? :-)