Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dga

Pages: 1 2 3 4 5 6 [7] 8 9
91
Update from about 15 minutes ago:  I just committed another change to the repository that eliminates a few more errors when trying to compile under Cygwin.  It also boosts performance by a fairly negligible amount, at least on compute_35 devices.  I didn't bother benchmarking the difference on other cards, because the gain was only about 20 c/m on a Tesla.  But, hopefully, this is one step closer to something that will build happily on Windows.

92
..So I guess that means "no" ?

It means "complicated"

Here's an example:  One of my systems that I've tested on is a new, nice Haswell-based machine from Dell.

CPU:  i7-4770
GPU:  GTX 650Ti

CPU hashing gets somewhere in the 330 c/s range using Yam.  Maybe more, maybe less, but in that range.
GPU hashing gets almost exactly the same.  I think I can sneak it a little higher in the next release, but for now, they're nearly identical.

The CPU costs $300.  Not counting motherboard and memory.

The GPU costs about $140, 1GB of DRAM included.

The CPU draws about 70-80W when running full tilt.  The GPU uses about 15-30W when running my code full speed.

You need one motherboard (~$120) and DRAM (~$40) for every CPU or two.  You can instead fit 3-6 GPUs into a motherboard, reducing those costs further.

Also, my code doesn't really take advantage of the zoominess of something like the 650Ti.   People have reported very good numbers from older cards.  The memory bandwidth and number of memory channels is pretty important here, and that's not increasing as radically fast as core counts.

In total, running PTS on a GPU probably costs 1/4th as much as doing it on a CPU.  That's not insignificant, but it's also not earth-shattering.  I suspect that given the current price of PTS and the hash rates, mining PTS on a CPU will actually remain power-profitable, which is more than you can say for most other options (DOGEcoin on a Haswell CPU isn't too bad, though.  *grin*)

As I said initially:  This doesn't (yet) change the game as radically for PTS as it did for things like Bitcoin.  The amount of memory accesses help level the game to a decent degree.  But I'll note that I think there's more room for optimization in the GPU code than the CPU code, so the gap will widen a bit more.

93
Dual GTX 690s:  2400 c/s at 115W at 10% CPU.
650Ti:  330-340 c/s at 1% CPU.
Macbook Pro with GT 650M:  200 c/s.
Tesla K20c:  ~800c/s.
My Xeon give me 200 c/m. And you write c/s. This error? How gpu miner faster cpu?

Gaaaaah, thanks.  Typo.  c/m.  c/m c/m c/m.

I'm too used to thinking in kh/s from the other coins.

  -Dave

94
DGA,
   Around here we don't do "contracts" but operate on the basis of trust and informal/non-binding agreements.  My entire trust with the community and valuation of PTS, AGS, and future in the bitcoin space is on the line and I am very well known.   So that is more of a guarantee than any signed contract, it is in my best interest to do right by everyone I deal with.
 
   It is nice that it is based on ptsminer so does that mean it works with standard pools?

   Post the code and when I hear feedback from those on the forum that it works I will pay you 160 PTS. 

Dan
   

Just wanted to follow up publicly to thank you for the bounty and to note that you were good on your word, as promised.  I appreciate it.

  -Dave

95
What arch should be for Quadro 4000 ?

Check out:
https://developer.nvidia.com/cuda-gpus

Compute capability 2.0 -> arch sm_20

96
The pool is http://ptsweb.beeeeer.org/ ?

Yeah, sorry - I just used the one ptsminer supported, which I used because it built easily on my mac.  *grin*

If anyone wants to send me a patch to make it work on ypool or other pools, I'm happy to incorporate it.

97
Good Work .
I would like to suggest you to build a gpu Miner and  take about  1% donation (like yvg1900) with every Worker . this would be good for you

We are waiting For Your Release  :)

I agree with you that that's the right way to go.  Unfortunately, I don't have the time to do it.

There's a *lot* of support and build-support that needs to be done for a working miner, and GPUs make it even more painful, as the threads here show.  yvv1900's yam miner is impressive not just because of its speed, but because he's made it easy to use and work well on a lot of platforms.  That takes a lot of attention to engineering -- quite probably more work to do that part than it is just to make a fast miner.  I think yvg deserves every 1% he gets out of his miner and that it's a great business model for supporting the development of the code.

I may ask the author of CudaMiner if he wants to do it together, though. :)

  -Dave

98
I'm facing this error:

using SSE4
Segmentation fault (core dumped)


my GPU is Quadro 5000 and CPU is Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz

Cuda 5.5

On unix, change the makefile.unix.  Look for where it says sm_30 and change it to sm_20
(for the GPU architecture in the nvcc compilation line)

  -Dave

99
All above with more than 20 posts are paid.

Giveaway is still open.

ok. :-)

Pr8cnhz5eDsUegBZD4VZmGDARcKaozWbBc

100
Code: [Select]
$ make -f makefile.unix
nvcc -O3 -c -arch=sm_30 -o obj/gpuhash.o gpuhash.cu
nvcc fatal   : Path to libdevice library not specified
make: *** [obj/gpuhash.o] Error 255

Any idea?

Urk, wow.  I've never seen that compile error.  Is your LD_LIBRARY_PATH set to include the cuda libs?  Often /usr/local/cuda-5.5/lib64

But I think this is a CUDA install problem.  Googling it suggests that the line

NVVMIR_LIBRARY_DIR = /usr/lib/nvidia-cuda-toolkit/libdevice
to /etc/nvcc.profile

fixed it for some people.

But that may not apply to you.  Are you using Debian?  If so, give that a shot, correcting the path as needed for the location of the cuda toolkit.

It's gentoo. I found them in /opt/cuda/*

Now:

Code: [Select]
$ make -f makefile.unix
nvcc -O3 -c -arch=sm_30 -o obj/gpuhash.o gpuhash.cu
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/stddef.h:214:32: fatal error: crt/device_runtime.h: No such file or directory
compilation terminated.
make: *** [obj/gpuhash.o] Error 1

Keeping you busy :)

Oh gentoo.  Um. 

The sledgehammer might be to try upgrading to gcc 4.8, but I realize that's a royal pain.  You're using the latest CUDA 5.5?

101
Instaled Ubuntu 12.04.3, libboost,  Yasm and CUDA

ERRO

g++ -c -O2 -fpermissive -o obj/cpuid.o cpuid.c
make: nvcc: Command not found

You don't have nvcc in your path.  You'll need to add it to your PATH and the path to the cuda libraries to your LD_LIBRARY_PATH.

if CUDADIR is the path to where you have cuda installed, in bash, do:

export PATH=$PATH:CUDADIR/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:CUDADIR/lib64

102
Got it working in an ubuntu instance but only getting 540 c/m “Kepler” GK104 / obviously I am doing something wrong

No, that's about what you should expect.

Glad it's working.

103
I have attempted to compile the code.  However, I get the following errors under cygwin 64..
 
make -f makefile.mingw64
yasm -f win64 -D WINABI -o obj/sha512_avx.o_asm intel/sha512_avx.asm
yasm -f win64 -D WINABI -o obj/sha512_sse4.o_asm intel/sha512_sse4.asm
g++ -c -O2 -march=athlon64 -mmmx -msse -msse2   -fpermissive -o obj/sha512.o_amd                               sha512.c
g++ -c -O1 -march=athlon64 -mmmx -msse -msse2   -fpermissive -o obj/sph_sha2.o_a                              md sph_sha2.c
g++ -c -O1 -march=athlon64 -mmmx -msse -msse2   -fpermissive -o obj/sph_sha2big.                              o_amd sph_sha2big.c
g++ -c -O2 -march=athlon64 -mmmx -msse -msse2  -mthreads -w -Wall -Wextra -Wform                              at -Wformat-security -Wno-unused-parameter  -DWIN32 -D_WINDOWS -DBOOST_THREAD_US                              E_LIB -DBOOST_SPIRIT_THREADSAFE  -I"/home/jng/cudapts-master/cudapts-master" -I"                              /usr/local/include" -o obj/main_poolminer.o_amd main_poolminer.cpp
main_poolminer.cpp:18:25: fatal error: sys/syscall.h: No such file or directory
 #include <sys/syscall.h>
                         ^
compilation terminated.
makefile.mingw64:66: recipe for target 'obj/main_poolminer.o_amd' failed
make: *** [obj/main_poolminer.o_amd] Error 1

i dont see a file in the github for syscall.h...also, how do I find the boost suffix?,  I am almost there, so your help is appreciated.


I am unable to build this as well I keep getting errors with CentOS and osfinder.sh..It seems to no be in the git golder so I downloaded another one but it still doesnt work.  I get errors just trying to run the scrip by it self ..I also tried the no chrono version.  THat seems to go much further but still fails. 
Any help and I will make a contribution to your effort. Thanks

1)  I've added osfinder.sh to the git repository.  Please re-pull.

2)  To the person trying on cygwin, I've removed the need for syscall.h in the most recent commit.  Go ahead and update and try again -- I'm not able to test on Cygwin, though, so it's likely you'll encounter further errors.

  -Dave

104
Code: [Select]
$ make -f makefile.unix
nvcc -O3 -c -arch=sm_30 -o obj/gpuhash.o gpuhash.cu
nvcc fatal   : Path to libdevice library not specified
make: *** [obj/gpuhash.o] Error 255

Any idea?

Urk, wow.  I've never seen that compile error.  Is your LD_LIBRARY_PATH set to include the cuda libs?  Often /usr/local/cuda-5.5/lib64

But I think this is a CUDA install problem.  Googling it suggests that the line

NVVMIR_LIBRARY_DIR = /usr/lib/nvidia-cuda-toolkit/libdevice
to /etc/nvcc.profile

fixed it for some people.

But that may not apply to you.  Are you using Debian?  If so, give that a shot, correcting the path as needed for the location of the cuda toolkit.

105
Hey, beeeeer folks - just a heads-up:  I released my GPU miner hard-coded to use beeeeer, as I based the source on ptsminer.

Hold on to your pants and have fun. :-)

  -Dave

WOOOT! Compiling ....

If it works well for you, please chime in on the main board thread to confirm that it's legit. :-)  Happy to help with compile issues for linux/macos.  I'm clueless about windows, but if you have tips, I can commit them.

Pages: 1 2 3 4 5 6 [7] 8 9