CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 840.

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: djm34 on December 12, 2015, 01:38:31 PM

Quote from: sp_ on December 12, 2015, 01:15:17 PM

Quote from: joblo on December 12, 2015, 12:02:28 PM

Since quark was the focus of the most recent changes it proves that cuda 7.5 can perform better than 6.5. I hope these results translate to the other algos.

I have showed that it can be done with quark.
I believe the other algos can be tuned faster as well with more work..

0.01 BTC guys. This is all I am asking

so you need donation because you believe it can be done ? Grin

Also called crowdfunding.

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: Grout on December 13, 2015, 03:34:19 AM

Quote from: sp_ on December 12, 2015, 01:15:17 PM

0.01 BTC guys. This is all I am asking

There you go

697ff02bb2d2e1589eb2b8c40cbfd5584f477cbfe4ff6a942076ee54b8888075

Thanks

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: bobben2 on December 13, 2015, 04:25:16 AM

Just sent you
867794d843b271e2647511eff2d959e928bee5642bf9e181b4c9ce66bbf904b7
Keep up the good work!

Thanks

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

I submitted another 30KHASH in the x13 algo on the 750ti. Still a few khash to reach the cuda 6.5 speed. (release 72)

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: AliMan on December 12, 2015, 10:45:15 PM

Quote from: djm34 on December 12, 2015, 03:35:58 PM

Quote from: scryptr on December 12, 2015, 02:38:31 PM

MINERS WILL DONATE FOR FRANKEN-WEENIE--

No waiting. Work on the purist executable at your own pace. Maybe DJM will flip out some useful code for neoscrypt. Maybe we will all just get along. --scryptr

hmm... You must mistake me for Santa Klaus Grin

Will see what I can do during christmas vacation... Cheesy

Yo, what's your fastest kernel speed for 980 on neoscrypt?

around 850kh/s OC

bobben2

full member

Activity: 279

Merit: 104

Quote from: sp_ on December 12, 2015, 01:15:17 PM

Quote from: joblo on December 12, 2015, 12:02:28 PM

Since quark was the focus of the most recent changes it proves that cuda 7.5 can perform better than 6.5. I hope these results translate to the other algos.

I have showed that it can be done with quark.
I believe the other algos can be tuned faster as well with more work..

0.01 BTC guys. This is all I am asking

Just sent you
867794d843b271e2647511eff2d959e928bee5642bf9e181b4c9ce66bbf904b7

Keep up the good work!

BTW: My newly acquired ASUS GTX 970 on stock clocks is mining Neoscrypt at ~ 470 kH/s.
cmd line: ccminer -t -a neoscrypt -o
Version spmod 1.5.63 and CUDA 6.5.19 on Xubuntu 12.04 x64. Is that what these cards can do or could it
go higher "with the current software"?

EDIT: Managed to get to ~ 490 kH/s by setting difficulty=256 recognised by the pool..

Grout

full member

Activity: 139

Merit: 100

Quote from: sp_ on December 12, 2015, 01:15:17 PM

0.01 BTC guys. This is all I am asking

There you go

697ff02bb2d2e1589eb2b8c40cbfd5584f477cbfe4ff6a942076ee54b8888075

AliMan

hero member

Activity: 1974

Merit: 502

Vave.com - Crypto Casino

Quote from: djm34 on December 12, 2015, 03:35:58 PM

Quote from: scryptr on December 12, 2015, 02:38:31 PM

MINERS WILL DONATE FOR FRANKEN-WEENIE--

No waiting. Work on the purist executable at your own pace. Maybe DJM will flip out some useful code for neoscrypt. Maybe we will all just get along. --scryptr

hmm... You must mistake me for Santa Klaus Grin

Will see what I can do during christmas vacation... Cheesy

Yo, what's your fastest kernel speed for 980 on neoscrypt?

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: scryptr on December 12, 2015, 02:38:31 PM

MINERS WILL DONATE FOR FRANKEN-WEENIE--

No waiting. Work on the purist executable at your own pace. Maybe DJM will flip out some useful code for neoscrypt. Maybe we will all just get along. --scryptr

hmm... You must mistake me for Santa Klaus Grin

Will see what I can do during christmas vacation... Cheesy

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: djm34 on December 12, 2015, 01:55:59 PM

Quote from: joblo on December 12, 2015, 01:33:52 PM

Quote from: pallas on December 12, 2015, 01:09:25 PM

Quote from: joblo on December 12, 2015, 01:00:27 PM

Quote from: pallas on December 12, 2015, 12:13:29 PM

I've found a solution to the neoscrypt problem: building a cuda 6.5/7.5 hybrid.
Tested working on Linux. Here's the procedure:

- build ccminer with cuda 7.5 as usual
- remove all the object files in the neoscrypt folder: rm neoscrypt/*.o
- edit Makefile
- replace all the instances of "7.5" with "6.5"
- run make again
- you just made a ccminer executable with all the algos on 7.5 except neoscrypt on 6.5 :-)
- revert the Makefile changes to build it again in the future

If you find this useful, please donate to the BTC address in my signature.

If I undertstand the result neo is compiled with 6.5 and eveyrthing else with 7.5. Then it is all linked
with 6.5. I'm not sure linking object files from different compilers is safe.

I prefer to use a script to select the prefered executable based on the algo. Less work, less risk, more
flexible.

Edit: but it's still a workaround. Wink

Linking object files from different compilers: I've often linked object files create with a C compiler and others created with an assembler.
In ccminer, some objects are compiled with gcc, some others with nvcc... you get the picture.

I get the picture. I got a pascal program to call a fortran subroutine several decades ago. No available linker could handle it I had to
link it manually.

The examples you gave are where it is explicitly supported by the respective linkers. I wouldn't expect that support in different
major versions of the same compiler. ABI changes can be introduced.

I'm not saying it can't be done, just that it's probably not supported and might not always work.

used for quite some time c++ programme linked to old fortran libraries, this was done automatically (well in a script).

Also regarding nvcc, there are different way to link and compile. You can very well compile one part or the other with one cuda version or another and do the linking with gcc (and I am not entirely sure, but I think for linking cuda is just calling the default compiler (gcc or visual stuff... so actually it doesn't really matter that you compile with various cuda version...

Just for kicks I googled it. nvcc does do a compatibility check on g++ (in the example below) versions so they do explicitly support
it and there are versions that don't work.

http://stackoverflow.com/questions/9421108/how-can-i-compile-cuda-code-then-link-it-to-a-c-project

I don't know for sure whether nvcc supports different versions of itself, it may have checked and passed in your case.
If I was a compiler developper it would be a very low priority as it would complicate changing the ABI and is generally only useful
when the original source code is not available.

scryptr

legendary

Activity: 1797

Merit: 1028

MINERS WILL DONATE FOR FRANKEN-WEENIE--

No waiting. Work on the purist executable at your own pace. Maybe DJM will flip out some useful code for neoscrypt. Maybe we will all just get along. --scryptr

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

Quote from: joblo on December 12, 2015, 02:18:48 PM

Quote from: sp_ on December 12, 2015, 12:28:25 PM

Quote from: joblo on December 12, 2015, 12:02:28 PM

Got the test results on a EVGA 980 reference standard clocks.
76-7.5 76-6.5 74-6.5 74-7.5
quark 19.9 19.3 19.3 19.7
x11 9850 9920 10000 7680
lyra2v2 10.7 11.4 11.6 10.9
neo 220 635 640 220

Thanks for testing. Can you please try to compile release 74 with x86 build and cuda 7.5?

Done, results included above. The quark rate with 74-7.5 was unexpected, some of the previous changes
must have provided a bigger improvement on cuda 7.5 than 6.5

My tuning rig doesn't contain a gtx 980. I only have 750ti, 960, 970x2. your results are different than mine in the quark algo.

As you can see I have optimized x11 30% faster(than release 74 compiled with cuda 7.5), but still slower than cuda 6.5.

(but only 4 of the 11 x11 kernals have been changed)

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: scryptr on December 12, 2015, 02:22:13 PM

Quote from: pallas on December 12, 2015, 01:18:08 PM

Quote from: sp_ on December 12, 2015, 12:54:52 PM

Quote from: pallas on December 12, 2015, 12:13:29 PM

I've found a solution to the neoscrypt problem: building a cuda 6.5/7.5 hybrid.

This is not a solution, this is a workaround.

I don't see a problem.
Most people already have both cuda 6.5 and 7.5.
With some little changes to the Makefile, you could compile each kernel with its best cuda version, in a single executable.

PLEASE POST THE FRANKEN-WEENIE WORKAROUND--

If you could post a Windows executable with the promised features, I'll donate. Quark is faster with release dot 76. I want to use the executable with NiceHash Miner and auto-switch. On Linux, I could compile it myself... but I don't have a working autoswitch script. --scryptr

I never built ccminer on windows. I don't even have a working windows environment with cuda and nvidia drivers. Sorry.
Maybe I could do a Makefile (or whatever) patch to make neoscrypt compile on 6.5 and post a pull request? That way sp_ can build the win binary for everybody. But I don't think he agrees on "the method".

scryptr

legendary

Activity: 1797

Merit: 1028

Quote from: pallas on December 12, 2015, 01:18:08 PM

Quote from: sp_ on December 12, 2015, 12:54:52 PM

Quote from: pallas on December 12, 2015, 12:13:29 PM

I've found a solution to the neoscrypt problem: building a cuda 6.5/7.5 hybrid.

This is not a solution, this is a workaround.

I don't see a problem.
Most people already have both cuda 6.5 and 7.5.
With some little changes to the Makefile, you could compile each kernel with its best cuda version, in a single executable.

PLEASE POST THE FRANKEN-WEENIE WORKAROUND--

If you could post a Windows executable with the promised features, I'll donate. Quark is faster with release dot 76. I want to use the executable with NiceHash Miner and auto-switch. On Linux, I could compile it myself... but I don't have a working autoswitch script. --scryptr

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: sp_ on December 12, 2015, 12:28:25 PM

Quote from: joblo on December 12, 2015, 12:02:28 PM

Got the test results on a EVGA 980 reference standard clocks.

      76-7.5 76-6.5 74-6.5 74-7.5
quark 19.9 19.3 19.3 19.7
x11    9850 9920    10000 7680
lyra2v2 10.7 11.4    11.6 10.9
neo    220    635 640 220

Thanks for testing. Can you please try to compile release 74 with x86 build and cuda 7.5?

Done, results included above. The quark rate with 74-7.5 was unexpected, some of the previous changes
must have provided a bigger improvement on cuda 7.5 than 6.5

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: joblo on December 12, 2015, 01:33:52 PM

Quote from: pallas on December 12, 2015, 01:09:25 PM

Quote from: joblo on December 12, 2015, 01:00:27 PM

Quote from: pallas on December 12, 2015, 12:13:29 PM

I've found a solution to the neoscrypt problem: building a cuda 6.5/7.5 hybrid.
Tested working on Linux. Here's the procedure:

- build ccminer with cuda 7.5 as usual
- remove all the object files in the neoscrypt folder: rm neoscrypt/*.o
- edit Makefile
- replace all the instances of "7.5" with "6.5"
- run make again
- you just made a ccminer executable with all the algos on 7.5 except neoscrypt on 6.5 :-)
- revert the Makefile changes to build it again in the future

If you find this useful, please donate to the BTC address in my signature.

If I undertstand the result neo is compiled with 6.5 and eveyrthing else with 7.5. Then it is all linked
with 6.5. I'm not sure linking object files from different compilers is safe.

I prefer to use a script to select the prefered executable based on the algo. Less work, less risk, more
flexible.

Edit: but it's still a workaround. Wink

Linking object files from different compilers: I've often linked object files create with a C compiler and others created with an assembler.
In ccminer, some objects are compiled with gcc, some others with nvcc... you get the picture.

I get the picture. I got a pascal program to call a fortran subroutine several decades ago. No available linker could handle it I had to
link it manually.

The examples you gave are where it is explicitly supported by the respective linkers. I wouldn't expect that support in different
major versions of the same compiler. ABI changes can be introduced.

I'm not saying it can't be done, just that it's probably not supported and might not always work.

used for quite some time c++ programme linked to old fortran libraries, this was done automatically (well in a script).

Also regarding nvcc, there are different way to link and compile. You can very well compile one part or the other with one cuda version or another and do the linking with gcc (and I am not entirely sure, but I think for linking cuda is just calling the default compiler (gcc or visual stuff... so actually it doesn't really matter that you compile with various cuda version...

djm34

legendary

Activity: 1400

Merit: 1050

Quote from: sp_ on December 12, 2015, 01:15:17 PM

Quote from: joblo on December 12, 2015, 12:02:28 PM

Since quark was the focus of the most recent changes it proves that cuda 7.5 can perform better than 6.5. I hope these results translate to the other algos.

I have showed that it can be done with quark.
I believe the other algos can be tuned faster as well with more work..

0.01 BTC guys. This is all I am asking

so you need donation because you believe it can be done ? Grin

joblo

legendary

Activity: 1470

Merit: 1114

Quote from: pallas on December 12, 2015, 01:09:25 PM

Quote from: joblo on December 12, 2015, 01:00:27 PM

Quote from: pallas on December 12, 2015, 12:13:29 PM

I've found a solution to the neoscrypt problem: building a cuda 6.5/7.5 hybrid.
Tested working on Linux. Here's the procedure:

- build ccminer with cuda 7.5 as usual
- remove all the object files in the neoscrypt folder: rm neoscrypt/*.o
- edit Makefile
- replace all the instances of "7.5" with "6.5"
- run make again
- you just made a ccminer executable with all the algos on 7.5 except neoscrypt on 6.5 :-)
- revert the Makefile changes to build it again in the future

If you find this useful, please donate to the BTC address in my signature.

If I undertstand the result neo is compiled with 6.5 and eveyrthing else with 7.5. Then it is all linked
with 6.5. I'm not sure linking object files from different compilers is safe.

I prefer to use a script to select the prefered executable based on the algo. Less work, less risk, more
flexible.

Edit: but it's still a workaround. Wink

Linking object files from different compilers: I've often linked object files create with a C compiler and others created with an assembler.
In ccminer, some objects are compiled with gcc, some others with nvcc... you get the picture.

I get the picture. I got a pascal program to call a fortran subroutine several decades ago. No available linker could handle it I had to
link it manually.

The examples you gave are where it is explicitly supported by the respective linkers. I wouldn't expect that support in different
major versions of the same compiler. ABI changes can be introduced.

I'm not saying it can't be done, just that it's probably not supported and might not always work.

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

//
// Generated by NVIDIA NVVM Compiler
//
// Compiler Build ID: CL-19805474
// Cuda compilation tools, release 7.5, V7.5.16
// Based on LLVM 3.4svn
//
cuda 6.5 is 1.5 years old.

1.5 year development of compiler technology.

I think we need this to reach the optimal kernal speed.. It worked in the quark kernal, and it should work in the others as well.

pallas

legendary

Activity: 2716

Merit: 1094

Black Belt Developer

Quote from: sp_ on December 12, 2015, 01:19:52 PM

Quote from: pallas on December 12, 2015, 01:18:08 PM

Quote from: sp_ on December 12, 2015, 12:54:52 PM

Quote from: pallas on December 12, 2015, 12:13:29 PM

I've found a solution to the neoscrypt problem: building a cuda 6.5/7.5 hybrid.

This is not a solution, this is a workaround.

I don't see a problem.
Most people already have both cuda 6.5 and 7.5.
With some little changes to the Makefile, you could compile each kernel with its best cuda version, in a single executable.

Don't you want to know if cuda7.5 can make your code faster?. A recoding is probobly required.

You can do both things.
On amd we've been doing this forever.

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 840. (Read 2347659 times)