Went something like
Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 207. (Read 3426932 times)
July 29, 2014, 06:44:54 PM
Yea, that's a serious bump for practically nothing. I was all "what the fsck did I break now" when I saw the hashrate after first build, then the yays started piling on...
Went something like
Went something like
July 29, 2014, 06:32:37 PM
How about posting your code and we can compare to see what you did differently?
Me just wants to get my grubby hands on it.
Me just wants to get my grubby hands on it.
Right, I cloned djm's latest and only modified doom.cu and created doom_luffa512.cu. And obviously you'll need to modify Makefile.am and the VC project files to include doom_luffa512.cu in the build. Built it and voila, ~80 MH/s per 750 Ti. Let me know how it turns out.
Source for both files here: http://pastebin.com/3kUMumEm
thanks tsiv & djm.
my rig (5x750Ti / Ubuntu 1404) went from:
275MH @ ~300W
to
400MH @ ~300W
July 29, 2014, 06:31:09 PM
How about posting your code and we can compare to see what you did differently?
Me just wants to get my grubby hands on it.
Me just wants to get my grubby hands on it.
Right, I cloned djm's latest and only modified doom.cu and created doom_luffa512.cu. And obviously you'll need to modify Makefile.am and the VC project files to include doom_luffa512.cu in the build. Built it and voila, ~80 MH/s per 750 Ti. Let me know how it turns out.
Source for both files here: http://pastebin.com/3kUMumEm
this :
Code:
#pragma unroll 8
for (int i = 7; i >= 0; i--) {
if (hash[i] > d_target[i]) {
if(position < i) {
position = i;
rc = false;
}
}
if (hash[i] < d_target[i]) {
if(position < i) {
position = i;
rc = true;
}
}
}
for (int i = 7; i >= 0; i--) {
if (hash[i] > d_target[i]) {
if(position < i) {
position = i;
rc = false;
}
}
if (hash[i] < d_target[i]) {
if(position < i) {
position = i;
rc = true;
}
}
}
give a gain of performance while this doesn't:
Code:
#pragma unroll 8
for (int i = 7; i >= 0; i--) {
if (Hash[i] > pTarget[i]) {
rc = false;
break;
}
if (Hash[i] < pTarget[i]) {
rc = true;
break;
}
}
for (int i = 7; i >= 0; i--) {
if (Hash[i] > pTarget[i]) {
rc = false;
break;
}
if (Hash[i] < pTarget[i]) {
rc = true;
break;
}
}
Now if someone has the explanations, I will be happy to hear it... (I would tend to believe that the second is faster....) but no...
It's all them capital letters, yo. Can't fit through them pipelines.
You've got the Hash array defined in the kernel and not still a pointer to gmem?
July 29, 2014, 06:30:37 PM
Intel 3570k overclocked to 4.5Ghz, 16Gb ram
2 770s @ 1254 Core - 3703 Memory
1 670 @ 1254 Core - 3416 Memory
Don't worry...I've been doing this for awhile.
I posted that mainly because of the performance increase, but up to you guys, doesn't matter to me.
2 770s @ 1254 Core - 3703 Memory
1 670 @ 1254 Core - 3416 Memory
Don't worry...I've been doing this for awhile.
I posted that mainly because of the performance increase, but up to you guys, doesn't matter to me.
Which version of windows?
No one is doubting your experience but typically blue screens are caused by hardware or driver issues.
Overclocking the cpu to much is one sure way of getting blue screens.
Looking forward to checking out your changes.
July 29, 2014, 06:28:40 PM
Windows 7 x64.
The blue screen were just caused by trying to play movies and listen to music while mining at full blast lol. =) (All 3 at the same time.)
All I mean't was there are some optimizations that can be done in visual studio that have not been touched / left at default in the current github.
Didn't mean anything by it. =)
The blue screen were just caused by trying to play movies and listen to music while mining at full blast lol. =) (All 3 at the same time.)
All I mean't was there are some optimizations that can be done in visual studio that have not been touched / left at default in the current github.
Didn't mean anything by it. =)
July 29, 2014, 06:24:45 PM
Intel 3570k overclocked to 4.5Ghz, 16Gb ram
2 770s @ 1254 Core - 3703 Memory
1 670 @ 1254 Core - 3416 Memory
Don't worry...I've been doing this for awhile.
I posted that mainly because of the performance increase, but up to you guys, doesn't matter to me.
2 770s @ 1254 Core - 3703 Memory
1 670 @ 1254 Core - 3416 Memory
Don't worry...I've been doing this for awhile.
I posted that mainly because of the performance increase, but up to you guys, doesn't matter to me.
Which version of windows?
No one is doubting your experience but typically blue screens are caused by hardware or driver issues.
Overclocking the cpu to much is one sure way of getting blue screens.
Looking forward to checking out your changes.
July 29, 2014, 06:17:49 PM
Intel 3570k overclocked to 4.5Ghz, 16Gb ram
2 770s @ 1254 Core - 3703 Memory
1 670 @ 1254 Core - 3416 Memory
Don't worry...I've been doing this for awhile.
I posted that mainly because of the performance increase, but up to you guys, doesn't matter to me.
Don't need anyone to diagnose my system crashing haha I just meant in general. It's rock stable, just mean't if I tried to go all crazy and watcha movie while mining and play music. Mining alone it doesn't crash either way.
2 770s @ 1254 Core - 3703 Memory
1 670 @ 1254 Core - 3416 Memory
Don't worry...I've been doing this for awhile.
I posted that mainly because of the performance increase, but up to you guys, doesn't matter to me.
Don't need anyone to diagnose my system crashing haha I just meant in general. It's rock stable, just mean't if I tried to go all crazy and watcha movie while mining and play music. Mining alone it doesn't crash either way.
July 29, 2014, 06:17:37 PM
Hello all!
Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
Just curious, do you have a cpu that doesn't support as or by chance running amd motherboard or cpu? Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
Windows 7 or 32 bit os?
) July 29, 2014, 06:14:49 PM
Hello all!
Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
Just curious, do you have a cpu that doesn't support aes or by chance running amd motherboard or cpu? Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
Windows 7 or 32 bit os?
July 29, 2014, 06:14:19 PM
Hello all!
Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
blue screens, never had any blue screen (but why not)Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
LOL your not pushing the cards enough then! Blue screens common when I try to push close to 1300/1520 on my 270x's lol
July 29, 2014, 06:07:53 PM
Hello all!
Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
blue screens, never had any blue screen (but why not) Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
July 29, 2014, 06:05:45 PM
Hello all!
Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
Anyone who is using the windows binary and/or compiling with Visual Studio for windows...there are some optimizations that can be done in the visual studio settings that as I have found increase the performance of the binary and reduce random crashing / blue screens (esp when trying to do other things while mining.)
If anyone is interested, here in a few minutes i'll upload my optimized Visual Studio project file and can compile the binaries and post them as well. (Compiled for Djms' latest github source)
I've been able to completely eliminate any crashing / blue screens I've been getting in the past, and it doesn't hurt performance either!
July 29, 2014, 06:00:45 PM
EPIC
Thanks tsiv cayars and djm
July 29, 2014, 05:51:21 PM
How about posting your code and we can compare to see what you did differently?
Me just wants to get my grubby hands on it.
Me just wants to get my grubby hands on it.
Right, I cloned djm's latest and only modified doom.cu and created doom_luffa512.cu. And obviously you'll need to modify Makefile.am and the VC project files to include doom_luffa512.cu in the build. Built it and voila, ~80 MH/s per 750 Ti. Let me know how it turns out.
Source for both files here: http://pastebin.com/3kUMumEm
this :
Code:
#pragma unroll 8
for (int i = 7; i >= 0; i--) {
if (hash[i] > d_target[i]) {
if(position < i) {
position = i;
rc = false;
}
}
if (hash[i] < d_target[i]) {
if(position < i) {
position = i;
rc = true;
}
}
}
for (int i = 7; i >= 0; i--) {
if (hash[i] > d_target[i]) {
if(position < i) {
position = i;
rc = false;
}
}
if (hash[i] < d_target[i]) {
if(position < i) {
position = i;
rc = true;
}
}
}
give a gain of performance while this doesn't:
Code:
#pragma unroll 8
for (int i = 7; i >= 0; i--) {
if (Hash[i] > pTarget[i]) {
rc = false;
break;
}
if (Hash[i] < pTarget[i]) {
rc = true;
break;
}
}
for (int i = 7; i >= 0; i--) {
if (Hash[i] > pTarget[i]) {
rc = false;
break;
}
if (Hash[i] < pTarget[i]) {
rc = true;
break;
}
}
Now if someone has the explanations, I will be happy to hear it... (I would tend to believe that the second is faster....) but no...
July 29, 2014, 05:35:31 PM
July 29, 2014, 05:27:01 PM
O dear lord I done forgot the flags for nvidia miners... is there a cheat sheet for them and do they work with All version that are out ( like the nvminer )
Another quick question, is there a reason why my temps and all that are not displayed? Using nvminer D6c or something along those lines and see nothing but a screen full of hash rates and nothing more, but I still would like to see what each card is doing.
Another quick question, is there a reason why my temps and all that are not displayed? Using nvminer D6c or something along those lines and see nothing but a screen full of hash rates and nothing more, but I still would like to see what each card is doing.
July 29, 2014, 04:06:10 PM
from suprnova
GPU Miners please try Port 5112 instead of 5111. So for GPU use:
stratum+tcp://doom.suprnova.cc:5112
and report any issues you have to support or in the bitcointalk.org thread. thanks !
Hashrate Display Bug on Port 5112 is now FIXED !
GPU Miners please try Port 5112 instead of 5111. So for GPU use:
stratum+tcp://doom.suprnova.cc:5112
and report any issues you have to support or in the bitcointalk.org thread. thanks !
Hashrate Display Bug on Port 5112 is now FIXED !
July 29, 2014, 04:05:00 PM
Hm, that's weird, I got that error before I put in the 340.43 beta drivers last night.
Ya, hopefully the new 340.52 drivers fix the problem
wow it worked and says unable to query number of cuda dievices! is an nvidia driver installed
3788 is in
EDIT: driver 340.43 will not work on mine that must b the problem
im going to try 340.52
Ya, hopefully the new 340.52 drivers fix the problem
wow it worked and says unable to query number of cuda dievices! is an nvidia driver installed
3788 is in
EDIT: driver 340.43 will not work on mine that must b the problem
im going to try 340.52
loading in now
that did it the new drivers worked thanks all
EDIT:but no older bat files work so im doomed lol ill have to roll back the drivers and say good bye to doom coin oooo well
July 29, 2014, 03:59:42 PM
How about posting your code and we can compare to see what you did differently?
Me just wants to get my grubby hands on it.
Me just wants to get my grubby hands on it.
Right, I cloned djm's latest and only modified doom.cu and created doom_luffa512.cu. And obviously you'll need to modify Makefile.am and the VC project files to include doom_luffa512.cu in the build. Built it and voila, ~80 MH/s per 750 Ti. Let me know how it turns out.
Source for both files here: http://pastebin.com/3kUMumEm
July 29, 2014, 03:37:40 PM
YACoin:
cudaminer.exe -l K430x8 -o stratum+tcp://yac.coinmine.pl:9088 -u censored.censored -p censored --algo=scrypt-jane:YAC
Gainward GTX 650 non-ti 1GB gddr5 Revision A2 128Bit buss not oc-ed installed all newest CUDA etc. drivers
K430x8 was found automaticly
Here is a pic of error message:
cudaminer.exe -l K430x8 -o stratum+tcp://yac.coinmine.pl:9088 -u censored.censored -p censored --algo=scrypt-jane:YAC
Gainward GTX 650 non-ti 1GB gddr5 Revision A2 128Bit buss not oc-ed installed all newest CUDA etc. drivers
K430x8 was found automaticly
Here is a pic of error message:
If you run with auto-tune do you get any errors ??
Do you use Intel Graphics for monitor output?
I have never mined YAC maybe someone more knowledgeable than me can help you with that coin
If auto-tune crashes too maybe something else is wrong? did you make any recent changes in hardware/drivers etc ?
With cuda there where bundled new Graphic Card Driver ,no hardware changes.
Yes I have rebooted win7 64 after cuda installed ,and yes I've selected x64 win7 cuda drivers for desktop.
It would not be such a big deal If minerd worked with YAC ,and moddified minerd(with some cpu extensions support) worked with stratum.
You should contact member IvanLabrie. He is expert in yacoin mining with nvidia.
Send him PM.
you should find some help also here:
http://www.overclock.net/t/1468166/gtx-750-ti-mining
Jump to: