BitShares Forum
Other => Graveyard => BitShares PTS => Topic started by: bytemaster on November 13, 2013, 06:24:42 pm
-
https://github.com/InvictusInnovations/coyote_miner
This miner is 4x faster than the miner I was using with my pool and might be faster than ypool. Give it a shot. It does not work with with my mining pool as I want to support standard pools and encourage decentralization.
We are working on a new mining pool to work with this miner.
Enjoy!
mac version http://the-iland.net/static/downloads/mac_gw_miner.0.1.0.tar.gz
linux version: http://the-iland.net/static/downloads/linux_gw_miner.0.1.0.tar.gz
win64 version: windows: http://the-iland.net/static/downloads/windows_gw_miner.0.1.0.zip
-
So is this purely a solo miner?
-
So is this purely a solo miner?
For now, though pools can be built around it.
-
Do you plan on incorporating these changes into your current pool?
-
Also did you miss some folders in your src?
include_directories( fc/include )
include_directories( sphlib-3.0/c)
CMake Error at CMakeLists.txt:46 (add_subdirectory):
add_subdirectory given source "fc" which is not an existing directory.
-
Also did you miss some folders in your src?
include_directories( fc/include )
include_directories( sphlib-3.0/c)
CMake Error at CMakeLists.txt:46 (add_subdirectory):
add_subdirectory given source "fc" which is not an existing directory.
See the readme... you must checkout fc
-
ByteMaster what version of linux is your test environment? Or are you doing this on mac?
-
ByteMaster what version of linux is your test environment? Or are you doing this on mac?
Mac, g++ 4.8
-
ByteMaster what version of linux is your test environment? Or are you doing this on mac?
Mac, g++ 4.8
Boost 1.54
-
Any ETA on your new pool? I'd prefer to support your pool/business as a whole...
-
Hmm. Keep getting errors on compiling FC with boost 1.54 installed.
[ 75%] Built target fc
Linking CXX executable test_aes
libfc.a(thread.cpp.o): In function `fc::context::context(void (*)(long), boost::coroutines::detail::standard_stack_allocator&, fc::thread*)':
thread.cpp:(.text._ZN2fc7contextC2EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE[_ZN2fc7contextC5EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE]+0xe3): undefined reference to `boost::coroutines::detail::standard_stack_allocator::default_stacksize()'
thread.cpp:(.text._ZN2fc7contextC2EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE[_ZN2fc7contextC5EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE]+0xfe): undefined reference to `boost::coroutines::detail::standard_stack_allocator::allocate(boost::coroutines::stack_context&, unsigned long)'
libfc.a(thread.cpp.o): In function `fc::context::~context()':
thread.cpp:(.text._ZN2fc7contextD2Ev[_ZN2fc7contextD5Ev]+0x2d): undefined reference to `boost::coroutines::detail::standard_stack_allocator::deallocate(boost::coroutines::stack_context&)'
collect2: error: ld returned 1 exit status
make[2]: *** [test_aes] Error 1
make[1]: *** [CMakeFiles/test_aes.dir/all] Error 2
make: *** [all] Error 2
-
I'm getting a different error:
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::get_current_thread_data()':
(.text+0x19d): undefined reference to `pthread_key_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::set_current_thread_data(boost::detail::thread_data_base*)':
(.text+0x1dd): undefined reference to `pthread_key_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::start_thread_noexcept()':
(.text+0x253): undefined reference to `pthread_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::start_thread_noexcept(boost::thread_attributes const&)':
(.text+0x2d2): undefined reference to `pthread_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::detach()':
(.text+0x61d): undefined reference to `pthread_detach'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::join_noexcept()':
(.text+0xfb2): undefined reference to `pthread_join'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::thread::do_try_join_until_noexcept(timespec const&, bool&)':
(.text+0x1180): undefined reference to `pthread_join'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::(anonymous namespace)::create_current_thread_tls_key()':
(.text+0x2b): undefined reference to `pthread_key_create'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::get_current_thread_data()':
(.text+0x1b6): undefined reference to `pthread_getspecific'
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libboost_thread.a(thread.o): In function `boost::detail::set_current_thread_data(boost::detail::thread_data_base*)':
(.text+0x1f6): undefined reference to `pthread_setspecific'
CMakeFiles/gw_miner.dir/bitcoin.cpp.o: In function `boost::asio::detail::posix_thread::~posix_thread()':
bitcoin.cpp:(.text._ZN5boost4asio6detail12posix_threadD2Ev[_ZN5boost4asio6detail12posix_threadD5Ev]+0x26): undefined reference to `pthread_detach'
CMakeFiles/gw_miner.dir/bitcoin.cpp.o: In function `boost::asio::detail::posix_thread::join()':
bitcoin.cpp:(.text._ZN5boost4asio6detail12posix_thread4joinEv[_ZN5boost4asio6detail12posix_thread4joinEv]+0x2b): undefined reference to `pthread_join'
CMakeFiles/gw_miner.dir/bitcoin.cpp.o: In function `boost::asio::detail::posix_thread::start_thread(boost::asio::detail::posix_thread::func_base*)':
bitcoin.cpp:(.text._ZN5boost4asio6detail12posix_thread12start_threadEPNS2_9func_baseE[_ZN5boost4asio6detail12posix_thread12start_threadEPNS2_9func_baseE]+0x29): undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
make[2]: *** [gw_miner] Error 1
make[1]: *** [CMakeFiles/gw_miner.dir/all] Error 2
make: *** [all] Error 2
-
Looks like it needs pthread to build on linux...
-
Hmm. Keep getting errors on compiling FC with boost 1.54 installed.
[ 75%] Built target fc
Linking CXX executable test_aes
libfc.a(thread.cpp.o): In function `fc::context::context(void (*)(long), boost::coroutines::detail::standard_stack_allocator&, fc::thread*)':
thread.cpp:(.text._ZN2fc7contextC2EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE[_ZN2fc7contextC5EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE]+0xe3): undefined reference to `boost::coroutines::detail::standard_stack_allocator::default_stacksize()'
thread.cpp:(.text._ZN2fc7contextC2EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE[_ZN2fc7contextC5EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE]+0xfe): undefined reference to `boost::coroutines::detail::standard_stack_allocator::allocate(boost::coroutines::stack_context&, unsigned long)'
libfc.a(thread.cpp.o): In function `fc::context::~context()':
thread.cpp:(.text._ZN2fc7contextD2Ev[_ZN2fc7contextD5Ev]+0x2d): undefined reference to `boost::coroutines::detail::standard_stack_allocator::deallocate(boost::coroutines::stack_context&)'
collect2: error: ld returned 1 exit status
make[2]: *** [test_aes] Error 1
make[1]: *** [CMakeFiles/test_aes.dir/all] Error 2
make: *** [all] Error 2
What version of boost?
-
I have updated the github repo, see if linux builds work for you now.
-
Had to update CMAKE and Boost
git clone git://cmake.org/cmake.git
cd cmake/cmake-2.8.12.1
./configure
make
make install
export CMAKE_ROOT=/usr/local/share/cmake-2.8.12.1
wget http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.tar.bz2/download
tar --bzip2 -xf /path/to/boost_1_55_0.tar.bz2
./bootstrap.sh
./b2
./b2 install
/usr/local/bin/cmake .
-
would love an exe/zip file if possible
-
We are working on windows binaries for you.
-
mac version http://the-iland.net/static/downloads/mac_gw_miner.0.1.0.tar.gz
-
120 HPM? What does that boil down to in HPM per CPU GHz? (e.g. Dual Core 3.2 GHz = 120 / 6.4)
-
120 HPM? What does that boil down to in HPM per CPU GHz? (e.g. Dual Core 3.2 GHz = 120 / 6.4)
120 HPM == CPM on a 3.4 GHz Intel Core i7 iMac 27-inch, Late 2012
-
.......coyote_miner2/coyote_miner/sphlib-3.0/c/sha2big.c:204:23: fatal error: md_helper.c: No such file or directory
? :(
-
.......coyote_miner2/coyote_miner/sphlib-3.0/c/sha2big.c:204:23: fatal error: md_helper.c: No such file or directory
? :(
git pull
-
With boost 1.54 on Debian, I am still getting this error when compiling FC:
Linking CXX executable test_aes
libfc.a(thread.cpp.o): In function `fc::context::context(void (*)(long), boost::coroutines::detail::standard_stack_allocator&, fc::thread*)':
thread.cpp:(.text._ZN2fc7contextC2EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE[_ZN2fc7contextC5EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE]+0xe3): undefined reference to `boost::coroutines::detail::standard_stack_allocator::default_stacksize()'
thread.cpp:(.text._ZN2fc7contextC2EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE[_ZN2fc7contextC5EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE]+0xfe): undefined reference to `boost::coroutines::detail::standard_stack_allocator::allocate(boost::coroutines::stack_context&, unsigned long)'
libfc.a(thread.cpp.o): In function `fc::context::~context()':
thread.cpp:(.text._ZN2fc7contextD2Ev[_ZN2fc7contextD5Ev]+0x2d): undefined reference to `boost::coroutines::detail::standard_stack_allocator::deallocate(boost::coroutines::stack_context&)'
collect2: error: ld returned 1 exit status
make[2]: *** [test_aes] Error 1
make[1]: *** [CMakeFiles/test_aes.dir/all] Error 2
make: *** [all] Error 2
Trying in ubuntu
-
120 HPM? What does that boil down to in HPM per CPU GHz? (e.g. Dual Core 3.2 GHz = 120 / 6.4)
120 HPM == CPM on a 3.4 GHz Intel Core i7 iMac 27-inch, Late 2012
I'm seeing that as a quad, so 3.4 x 4 = 13.6.
120 HPM / 13.6 = ~8.8 HPM/GHz
Not too shabby. I've been doing some tests and managed to pull a steady ~7 HPM/GHz.
-
With boost 1.54 on Debian, I am still getting this error when compiling FC:
Linking CXX executable test_aes
libfc.a(thread.cpp.o): In function `fc::context::context(void (*)(long), boost::coroutines::detail::standard_stack_allocator&, fc::thread*)':
thread.cpp:(.text._ZN2fc7contextC2EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE[_ZN2fc7contextC5EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE]+0xe3): undefined reference to `boost::coroutines::detail::standard_stack_allocator::default_stacksize()'
thread.cpp:(.text._ZN2fc7contextC2EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE[_ZN2fc7contextC5EPFvlERN5boost10coroutines6detail24standard_stack_allocatorEPNS_6threadE]+0xfe): undefined reference to `boost::coroutines::detail::standard_stack_allocator::allocate(boost::coroutines::stack_context&, unsigned long)'
libfc.a(thread.cpp.o): In function `fc::context::~context()':
thread.cpp:(.text._ZN2fc7contextD2Ev[_ZN2fc7contextD5Ev]+0x2d): undefined reference to `boost::coroutines::detail::standard_stack_allocator::deallocate(boost::coroutines::stack_context&)'
collect2: error: ld returned 1 exit status
make[2]: *** [test_aes] Error 1
make[1]: *** [CMakeFiles/test_aes.dir/all] Error 2
make: *** [all] Error 2
Trying in ubuntu
Hey.. that is linking an exe you do not need!
-
update fc and the miner now and I removed the extra lib you don't need to build.
-
On debian 7 :
me@valinor:/tmp/coyote_miner$ cmake .
-- The C compiler identification is GNU 4.7.2
-- The CXX compiler identification is GNU 4.7.2
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error at CMakeLists.txt:2 (cmake_minimum_required):
CMake 2.8.10 or higher is required. You are running version 2.8.9
-
On debian 7 :
me@valinor:/tmp/coyote_miner$ cmake .
-- The C compiler identification is GNU 4.7.2
-- The CXX compiler identification is GNU 4.7.2
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error at CMakeLists.txt:2 (cmake_minimum_required):
CMake 2.8.10 or higher is required. You are running version 2.8.9
See above. You need to install the latest version of cmake and boost
-
Thanks just saw your post when the page refreshed, dunno how I missed it !
-
I am getting 42 HPM on a Quad DO machine.
-
on a AMD Opteron(tm) Processor 4171 HE (8 cores)
Usage: ./gw_miner HOST USER PASS
Performing Benchmark...
13.0319 hpm
24.5904 hpm
17.8479 hpm
18.6269 hpm
19.0899 hpm
22.6576 hpm
25.2702 hpm
32.2715 hpm
35.5816 hpm
34.2171 hpm
33.1173 hpm
33.8781 hpm
34.5473 hpm
36.5886 hpm
36.9985 hpm
34.7708 hpm
35.222 hpm
35.6342 hpm
35.9993 hpm
-
linux version: http://the-iland.net/static/downloads/linux_gw_miner.0.1.0.tar.gz
-
on a AMD Opteron(tm) Processor 4171 HE (8 cores)
Usage: ./gw_miner HOST USER PASS
Performing Benchmark...
13.0319 hpm
24.5904 hpm
17.8479 hpm
18.6269 hpm
19.0899 hpm
22.6576 hpm
25.2702 hpm
32.2715 hpm
35.5816 hpm
34.2171 hpm
33.1173 hpm
33.8781 hpm
34.5473 hpm
36.5886 hpm
36.9985 hpm
34.7708 hpm
35.222 hpm
35.6342 hpm
35.9993 hpm
You have to let it run longer than that for an accurate measure because not all seeds produce the same number of results. Let it finish the benchmark to get an accurate comparison. Those are cumulative averages, not independent samples.
-
windows: http://the-iland.net/static/downloads/windows_gw_miner.0.1.0.zip
i7 3820@3.6/3.8 100 HPM
-
I get this when compiling on 10.9:
warning: unknown warning option '-Wno-unused-local-typedefs' [-Wunknown-warning-option]
/Users/deweydb/Dev/coyote_miner/sphlib-3.0/c/sha2big.c:204:10: fatal error: 'md_helper.c' file not found
#include "md_helper.c"
^
1 warning and 1 error generated.
-
I get this when compiling on 10.9:
warning: unknown warning option '-Wno-unused-local-typedefs' [-Wunknown-warning-option]
/Users/deweydb/Dev/coyote_miner/sphlib-3.0/c/sha2big.c:204:10: fatal error: 'md_helper.c' file not found
#include "md_helper.c"
^
1 warning and 1 error generated.
Make sure you pull the latest, it was missing in an earlier checkin.
-
Had to update CMAKE and Boost
git clone git://cmake.org/cmake.git
cd cmake/cmake-2.8.12.1
./configure
make
make install
export CMAKE_ROOT=/usr/local/share/cmake-2.8.12.1
wget http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.tar.bz2/download
tar --bzip2 -xf /path/to/boost_1_55_0.tar.bz2
./bootstrap.sh
./b2
./b2 install
/usr/local/bin/cmake -DBOOST_ROOT=/path/to/boost_1_55_0 .
Added in the step to use the updated version of boost
-
Not finding much in the way of speed improvements
14.8261 hpm
28.9676 hpm
22.3346 hpm
23.9403 hpm
25.1426 hpm
30.388 hpm
34.3772 hpm
44.3091 hpm
48.7179 hpm
47.0896 hpm
46.0226 hpm
47.3313 hpm
48.5786 hpm
47.1027 hpm
48.0321 hpm
44.8933 hpm
45.8726 hpm
vs 200hpm using the jhProtominer
-
Make sure you pull the latest, it was missing in an earlier checkin.
If it's running correctly, should there be some text output?
-
Not finding much in the way of speed improvements
14.8261 hpm
28.9676 hpm
22.3346 hpm
23.9403 hpm
25.1426 hpm
30.388 hpm
34.3772 hpm
44.3091 hpm
48.7179 hpm
47.0896 hpm
46.0226 hpm
47.3313 hpm
48.5786 hpm
47.1027 hpm
48.0321 hpm
44.8933 hpm
45.8726 hpm
vs 200hpm using the jhProtominer
System and OS? Is that while operational or in the benchmark?
-
Make sure you pull the latest, it was missing in an earlier checkin.
If it's running correctly, should there be some text output?
Yes, with no args it should print the benchmark.
-
i7 980 windows 8
new coyote -110 hpm
coyote miner 37hpm
jhProtominer 150hpm
-
Can anyone provide info on how to setup this with solo mining?
-
Not finding much in the way of speed improvements
14.8261 hpm
28.9676 hpm
22.3346 hpm
23.9403 hpm
25.1426 hpm
30.388 hpm
34.3772 hpm
44.3091 hpm
48.7179 hpm
47.0896 hpm
46.0226 hpm
47.3313 hpm
48.5786 hpm
47.1027 hpm
48.0321 hpm
44.8933 hpm
45.8726 hpm
vs 200hpm using the jhProtominer
How many cores are you using with jhProtominer.... this still requires running 1 instance per 8 cores.
-
Can anyone provide info on how to setup this with solo mining?
Launch your
ProtoSHares-Qt.exe -server -rpcuser=user -rpcpassword=pass
./gw_miner.exe localhost user pass
-
Not finding much in the way of speed improvements
44.8933 hpm
45.8726 hpm
vs 200hpm using the jhProtominer
System and OS? Is that while operational or in the benchmark?
Both - Debian x64 8vcpu 8gb ram
-
How many cores are you using with jhProtominer.... this still requires running 1 instance per 8 cores.
Both are set at 8 cores to keep things equalized.
-
Did you compile in release mode? Something doesn't add up because I can get 40 HPM on digital ocean (quad core).
-
hey bytemaster any idea about this error?
http://bitsharestalk.org/index.php?topic=573.msg5661#msg5661
i found this random file on the net and put it in that directory and it seems to compile.
http://www.iis.ee.ethz.ch/~sha3/gmu_sha2/simvectors/md_helper.c.html
So maybe your repo is just missing that file?
-
hey bytemaster any idea about this error?
http://bitsharestalk.org/index.php?topic=573.msg5661#msg5661
i found this random file on the net and put it in that directory and it seems to compile.
http://www.iis.ee.ethz.ch/~sha3/gmu_sha2/simvectors/md_helper.c.html
So maybe your repo is just missing that file?
git pull fixes that.
-
Ahhh thanks! now how do i compile in release mode? i only get 60 HPM on i7 4.5GHz
-
cmake . -DCMAKE_BUILD_TYPE=Release
-
Please only report numbers from the benchmark... it may run slower doing getwork requests until I pipeline it. Also, please let it finish the benchmark.
-
debug vs release gives about 7hpm difference. 40 vs 47.
-
benchmark? what benchmark? where do i find this? still getting only ~60HPM with i7 4.5 GHZ and built with:
cmake . -DCMAKE_BUILD_TYPE=Release
-
Any ideas?
[ 1%] Building CXX object CMakeFiles/fc.dir/src/thread/thread.cpp.o
In file included from /usr/local/include/boost/atomic/detail/platform.hpp:22:0,
from /usr/local/include/boost/atomic/atomic.hpp:17,
from /usr/local/include/boost/atomic.hpp:12,
from /usr/local/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/local/include/boost/thread/once.hpp:20,
from /usr/local/include/boost/thread.hpp:17,
from /root/fc/src/thread/thread_d.hpp:4,
from /root/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp: In member function âvoid fc::thread_d::process_tasks()â:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for â__atomic_exchangeâ
make[2]: *** [CMakeFiles/fc.dir/src/thread/thread.cpp.o] Error 1
make[1]: *** [CMakeFiles/fc.dir/all] Error 2
-
Any ideas?
[ 1%] Building CXX object CMakeFiles/fc.dir/src/thread/thread.cpp.o
In file included from /usr/local/include/boost/atomic/detail/platform.hpp:22:0,
from /usr/local/include/boost/atomic/atomic.hpp:17,
from /usr/local/include/boost/atomic.hpp:12,
from /usr/local/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/local/include/boost/thread/once.hpp:20,
from /usr/local/include/boost/thread.hpp:17,
from /root/fc/src/thread/thread_d.hpp:4,
from /root/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp: In member function âvoid fc::thread_d::process_tasks()â:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for â__atomic_exchangeâ
make[2]: *** [CMakeFiles/fc.dir/src/thread/thread.cpp.o] Error 1
make[1]: *** [CMakeFiles/fc.dir/all] Error 2
Thats a new one... what type of system ? Boost version? That bug looks like it is in the boost code.
-
debug vs release gives about 7hpm difference. 40 vs 47.
How long did you let the benchmark run?
-
Boost version: 1.55.0
Boost include path: /usr/include
Could not find the following static Boost libraries:
boost_context
Some (but not all) of the required Boost libraries were found. You may need to install these additional Boost libraries. Alternatively, set BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT to the location of Boost.
** for a debug build: cmake -DCMAKE_BUILD_TYPE=Debug ..
Seems there is a fcontext.hpp in /usr/include/boost but no context
-
Win7 x64, i7-2600k @ 4.7Ghz
Benchmark Results: Between 138 and 159 hpm. Elasped time 133.382 seconds.
-
Win7 x64, i7-2600k @ 4.7Ghz
Benchmark Results: Between 138 and 159 hpm. Elasped time 133.382 seconds.
What was the final number... it is cumulative... can you compare to ypool?
-
Win7 x64, i7-2600k @ 4.7Ghz
Benchmark Results: Between 138 and 159 hpm. Elasped time 133.382 seconds.
What was the final number... it is cumulative...
143.something hpm I only roughly glanced thru the figures. I mostly ran the linux protominer (yPool), that average is 160hpm. My pc is dual boot linux/windows.
-
Win7 x64, i7-2600k @ 4.7Ghz
Benchmark Results: Between 138 and 159 hpm. Elasped time 133.382 seconds.
What was the final number... it is cumulative...
143.something hpm I only roughly glanced thru the figures
Ok, well at least that is in the ballpark of my numbers.
-
Any ideas?
[ 1%] Building CXX object CMakeFiles/fc.dir/src/thread/thread.cpp.o
In file included from /usr/local/include/boost/atomic/detail/platform.hpp:22:0,
from /usr/local/include/boost/atomic/atomic.hpp:17,
from /usr/local/include/boost/atomic.hpp:12,
from /usr/local/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/local/include/boost/thread/once.hpp:20,
from /usr/local/include/boost/thread.hpp:17,
from /root/fc/src/thread/thread_d.hpp:4,
from /root/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp: In member function âvoid fc::thread_d::process_tasks()â:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for â__atomic_exchangeâ
make[2]: *** [CMakeFiles/fc.dir/src/thread/thread.cpp.o] Error 1
make[1]: *** [CMakeFiles/fc.dir/all] Error 2
Thats a new one... what type of system ? Boost version? That bug looks like it is in the boost code.
Ubuntu 13.04 x64, fresh install of Boost from sources.
I'll try a fresh VPS and see if that helps.
-
Hey bytemaster, i'm sorry, it does run really fast! I thought i had enabled release mode by setenv, but apparently that didn't work.
I'm getting 113 HPM now on an i7 2600k OC'd to 4.5GHZ.
-
Hey bytemaster, i'm sorry, it does run really fast! I thought i had enabled release mode by setenv, but apparently that didn't work.
I'm getting 113 HPM now on an i7 2600k OC'd to 4.5GHZ.
Great! So how close am I to ypool?
-
This what I am seeing on my rMPB:
ACCEPTED: 0
ACCEPTED: 0
ACCEPTED: 0
ACCEPTED: 0
HPM: 146.101
-
it seems to hash the same, but i can't actually get it to connect to wallet to mine???
-
when run without options (doesn't connect) on 1090t w 8gigs of mem ~70-80 hpm....
-
When I run it without arguments, it benchmarks. But when I try to connect to localhost, it reports this:
./gw_miner localhost x y
/root/coyote_miner/bitcoin.cpp(88): Throw in function boost::property_tree::ptree bitcoin::detail::client::request(const string&)
Dynamic exception type: boost::exception_detail::clone_impl<bitcoin::exception>
std::exception::what: bitcoin::exception
[bitcoin::bitcoin_msg_*] = Response returned with status code 500
I installed boost 1.53 development and debug so that should include all the boost libraries. Any ideas?
EDIT: stopping and starting bitcoind a few times and trying again resolves the issue.
Also, occasionally it will display hashes, but still say "ACCEPTED: 0." Is this normal?
-
Yes... that is normal. I submit hashes below a certain threshold automatically... when it finds a block it will say accepted 1.
-
Sorry to say, that I think Ypool still has the edge.
My i7 2600k is benching at 79 while ypool is hovering around 85.
-
Got it installed on Arch. Benchmark runs fine... 140-150HPM 136.363 seconds on i5 3570K at 4.2GHz.
When I try to run with ./gw_miner localhost USER PASS
it just says: ./gw_miner: /usr/lib/libcrypto.so.1.0.0: no version information available (required by ./gw_miner)
and runs at 100% on 1 core.
Am I doing something wrong?
-
Hey bytemaster, i'm sorry, it does run really fast! I thought i had enabled release mode by setenv, but apparently that didn't work.
I'm getting 113 HPM now on an i7 2600k OC'd to 4.5GHZ.
Great! So how close am I to ypool?
I can't actually run ypool's miner on OSX, i haven't figured out how to do that yet, is it even possible?
-
With this are we able to point more then one computer at our qt wallet?
-
With this are we able to point more then one computer at our qt wallet?
Yes
-
It looked like I was able to mine to the same computer over IP, but even though it was reporting a hashrate it was using 0% of the cpu, so I switched to each computer mining to their own wallet.
I'm seeing something worrisome, though. A bunch of miners will simultaneously show that they calculated the exact same hash! I imagine this implies there is a ton of duplicated effort. I've seen this quite a few times. Is there a way to get them to work on different problems? If I connect them to the same wallet through IP, would that fix it?
-
i7-4770 (4GB,1 Chip) - 121 hpm (cpm??)
i7-3770 (8GB,2 Chip) - 132 hpm
Core 2 Duo - T6600 - 21 hpm
Interesting that the i7-3770 should outperform the i7-4770, I put this down to its memory being spread out over 2 chips.
Older machines achieve a much lower cpm obviously, but I think at reasonable power usage levels - so hoping we'll see large pools of old computers from individual miners, rather than capital intensive commercial mining.
-
Launch your
ProtoSHares-Qt.exe -server -rpcuser=user -rpcpassword=pass
./gw_miner.exe localhost user pass
I launched my wallet with the first line and then the solo miner with the second line.
The wallet started up successfully, but the miner did not output anything, and CPU usage rate kept 0%.
What happened here? Running Windows Server 2008 R2
-
Launch your
ProtoSHares-Qt.exe -server -rpcuser=user -rpcpassword=pass
./gw_miner.exe localhost user pass
I launched my wallet with the first line and then the solo miner with the second line.
The wallet started up successfully, but the miner did not output anything, and CPU usage rate kept 0%.
What happened here? Running Windows Server 2008 R2
Start the miner like this. Change to your own username and password.
ProtoShares-Qt.exe -server -rpcuser=your_own_user -rpcpassword=your_own_password
gw_miner.exe localhost your_own_user your_own_password
-
Start the miner like this. Change to your own username and password.
ProtoShares-Qt.exe -server -rpcuser=your_own_user -rpcpassword=your_own_password
gw_miner.exe localhost your_own_user your_own_password
I tried that, the wallet is OK as always, and neither the miner have any output nor the %CPU gains.
Looks like the miner failed to connect to the wallet but did not crash.
Also I am using the latest version of wallet.
-
Start the miner like this. Change to your own username and password.
ProtoShares-Qt.exe -server -rpcuser=your_own_user -rpcpassword=your_own_password
gw_miner.exe localhost your_own_user your_own_password
I tried that, the wallet is OK as always, and neither the miner have any output nor the %CPU gains.
Looks like the miner failed to connect to the wallet but did not crash.
Also I am using the latest version of wallet.
Did you previously create a protoshares.conf file?
-
Did you previously create a protoshares.conf file?
Yes, I also tried the RPC credentials in my conf file, same result.
-
Did you previously create a protoshares.conf file?
Yes, I also tried the RPC credentials in my conf file, same result.
Inside your .conf file if you have -rpcport inside, delete it. Restart wallet and try the mining client again. Make it something like this.
rpcuser=your_username
rpcpassword=your_password
rpcallowip=127.0.0.1
server=1
-
Inside your .conf file if you have -rpcport inside, delete it. Restart wallet and try the mining client again. Make it something like this.
rpcuser=your_username
rpcpassword=your_password
rpcallowip=127.0.0.1
server=1
Had the "rpcport" line deleted and it worked! Thanks!
My configuration was given by others and I did not notice this.
-
Hello everyone. I'm trying to run a miner and it does not work. Wallet run like a server.
My conffile is:
server=1
rpcuser=login
rpcpassword=pass
rpcallowip=127.0.0.1
My bat-file is:
gw_miner.exe 127.0.0.1 -u login -p pass
pause
Its not work. I have this:
(http://s53.radikal.ru/i139/1311/83/dd0f5c6ee136.jpg) (http://radikal.ru/fp/bb09eb7147d6472aaf9a3f5ac1664e28)
-
All work. :D
-
Hello everyone. I'm trying to run a miner and it does not work. Wallet run like a server.
My conffile is:
server=1
rpcuser=login
rpcpassword=pass
rpcallowip=127.0.0.1
My bat-file is:
gw_miner.exe 127.0.0.1 -u login -p pass
pause
Its not work. I have this:
You should run the miner as: gw_miner.exe 127.0.0.1 login pass
and not as: gw_miner.exe 127.0.0.1 -u login -p pass
-
Just curious. Anyone solo mining with this miner have managed to mined a block yet?
-
Solo mining is not profitable, if you use this you should have your own mini farm.
I have 15 macs, that combined only have the expectation to earn 1 block per day. If you solo mine right now with a high end machine you should expect one block every 2 weeks. Of course the difficulty will rise over 2 weeks and orphans are high, so solo mining is more like one block every month+.
I just pushed a patch to gain another 10%
https://github.com/InvictusInnovations/coyote_miner
-
I get this message on make:
In file included from /usr/local/include/boost/atomic/detail/platform.hpp:22:0,
from /usr/local/include/boost/atomic/atomic.hpp:17,
from /usr/local/include/boost/atomic.hpp:12,
from /usr/local/include/boost/thread/pthread/once_atomic.hpp:20,
from /usr/local/include/boost/thread/once.hpp:20,
from /usr/local/include/boost/thread.hpp:17,
from /home/ubuntu/coyote_miner_update/fc/src/thread/thread_d.hpp:4,
from /home/ubuntu/coyote_miner_update/fc/src/thread/thread.cpp:5:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp: In member function ‘void fc::thread_d::process_tasks()’:
/usr/local/include/boost/atomic/detail/gcc-atomic.hpp:1081:95: error: invalid memory model for ‘__atomic_exchange’
return __atomic_exchange_n(&v_, v, atomics::detail::convert_memory_order_to_gcc(order));
^
make[2]: *** [fc/CMakeFiles/fc.dir/src/thread/thread.cpp.o] Error 1
make[1]: *** [fc/CMakeFiles/fc.dir/all] Error 2
make: *** [all] Error 2
I'm using Boost 1.55
Switched to Boost 1.54, compiles fine.
-
https://github.com/InvictusInnovations/coyote_miner
This miner is 4x faster than the miner I was using with my pool and might be faster than ypool. Give it a shot. It does not work with with my mining pool as I want to support standard pools and encourage decentralization.
We are working on a new mining pool to work with this miner.
Enjoy!
mac version http://the-iland.net/static/downloads/mac_gw_miner.0.1.0.tar.gz
linux version: http://the-iland.net/static/downloads/linux_gw_miner.0.1.0.tar.gz
win64 version: windows: http://the-iland.net/static/downloads/windows_gw_miner.0.1.0.zip
Honestly, I'm a noob at this, but am really excited about the opportunity to be apart of this. I need help getting this miner to run on my Mac 10.6.8 OSX. When I open the download, it takes me to the Terminal, and I get an "Illegal instruction" error. Can anyone help me with this?
-
Solo mining is not profitable, if you use this you should have your own mini farm.
I have 15 macs, that combined only have the expectation to earn 1 block per day. If you solo mine right now with a high end machine you should expect one block every 2 weeks. Of course the difficulty will rise over 2 weeks and orphans are high, so solo mining is more like one block every month+.
I just pushed a patch to gain another 10%
https://github.com/InvictusInnovations/coyote_miner
I git pulled and recompiled, trying it out now, seems to be a bit faster. Can you tell me though, is it usual that this miner should use such small amount of memory? It's only using about 1.5 GB of memory, can i increase this amount? will increasing it add any benefit to mining speed?
-
Increasing memory will hurt performance, due to increased cache misses.
-
https://github.com/InvictusInnovations/coyote_miner
This miner is 4x faster than the miner I was using with my pool and might be faster than ypool. Give it a shot. It does not work with with my mining pool as I want to support standard pools and encourage decentralization.
We are working on a new mining pool to work with this miner.
Enjoy!
mac version http://the-iland.net/static/downloads/mac_gw_miner.0.1.0.tar.gz
linux version: http://the-iland.net/static/downloads/linux_gw_miner.0.1.0.tar.gz
win64 version: windows: http://the-iland.net/static/downloads/windows_gw_miner.0.1.0.zip
Honestly, I'm a noob at this, but am really excited about the opportunity to be apart of this. I need help getting this miner to run on my Mac 10.6.8 OSX. When I open the download, it takes me to the Terminal, and I get an "Illegal instruction" error. Can anyone help me with this?
Do you have an old 32 bit mac? These are 64 bit only.
-
Solo mining is not profitable, if you use this you should have your own mini farm.
I have 15 macs, that combined only have the expectation to earn 1 block per day. If you solo mine right now with a high end machine you should expect one block every 2 weeks. Of course the difficulty will rise over 2 weeks and orphans are high, so solo mining is more like one block every month+.
I just pushed a patch to gain another 10%
https://github.com/InvictusInnovations/coyote_miner
Hi,
Thanks for the update and the great work. Would you mind giving some basic guidelines how to build your miner for windows.
-
Increasing memory will hurt performance, due to increased cache misses.
Weird, i thought that protoshares were supposed to be very memory heavy. Will the 1.5 GB requirement increase as the difficulty goes up? What would be the most ideal setup for mining protoshares then? What is more important fast RAM or RAM timings? Is a large CPU Cache important?
Thanks!
-
Just curious. Anyone solo mining with this miner have managed to mined a block yet?
the same question, anyone got a block with this miner?
-
Solo mining is not profitable, if you use this you should have your own mini farm.
I have 15 macs, that combined only have the expectation to earn 1 block per day. If you solo mine right now with a high end machine you should expect one block every 2 weeks. Of course the difficulty will rise over 2 weeks and orphans are high, so solo mining is more like one block every month+.
I just pushed a patch to gain another 10%
https://github.com/InvictusInnovations/coyote_miner
May I have a new patched Linux binary please?
Trying hard to compile from source and now I am stuck with Boost 1.54 installation...
I am using Ubuntu 13.10 x64.
-
Increasing memory will hurt performance, due to increased cache misses.
Weird, i thought that protoshares were supposed to be very memory heavy. Will the 1.5 GB requirement increase as the difficulty goes up? What would be the most ideal setup for mining protoshares then? What is more important fast RAM or RAM timings? Is a large CPU Cache important?
Thanks!
Want to know it too!
-
We targeted 1 GB of memory to do the proof of work and to limit the amount of parallelism that you could employ with that 1 GB. Unless you have more than 8 cores, that is all the memory required. If you have 32 cores, then you will need 4 GB of memory. So it scales with CPU, but adding more memory in itself does not help beyond a certain point.
-
We targeted 1 GB of memory to do the proof of work and to limit the amount of parallelism that you could employ with that 1 GB. Unless you have more than 8 cores, that is all the memory required. If you have 32 cores, then you will need 4 GB of memory. So it scales with CPU, but adding more memory in itself does not help beyond a certain point.
Can you publish updated Windows version?
-
It is very difficult to compile from the sources.
Can someone write step by step instructions for Ubuntu(12 or 13)?
bytemaster
Can you explain how to compile your miner? THANK YOU
-
I've tried for solo mine.
I'm managed to go through connection problems, but have a few nodes with dual Xeon 2450L (32 threads total) and I have a very low CPU usage - between 25 and 60%
I suppose the miner is not optimized for such CPU count, can anything be done on this?
-
I've tried for solo mine.
I'm managed to go through connection problems, but have a few nodes with dual Xeon 2450L (32 threads total) and I have a very low CPU usage - between 25 and 60%
I suppose the miner is not optimized for such CPU count, can anything be done on this?
Start it more than once...
-
Too bad this isnt really worth it anymore, would have needed that one a week ago -.-
Even with my 14 (physical) machines i only get to 1600 hpm which results in a block every 4 days, thats too much to be comfortable - might not even be a single block within diff retarget.
-
I've tried for solo mine.
I'm managed to go through connection problems, but have a few nodes with dual Xeon 2450L (32 threads total) and I have a very low CPU usage - between 25 and 60%
I suppose the miner is not optimized for such CPU count, can anything be done on this?
Start it more than once...
Started 4 instances. Alas, didn't get the 99% flat line on CPU usage or nowhere near it.
Even with 4 instances, getting aroung 200 hpm total from all ~75% cpu usage. A single 3930k goes to 180 hpm.
-
Can we get a Windows 32-bit version? I'm having serious trouble building it myself.
-
Getting the following when I try to build:
C:\Users\Wolf\Desktop\coyote_miner>cmake . -DCMAKE_BUILD_TYPE=Release -DOPENSSL_
LIBRARIES=C:\Users\Wolf\Desktop\vc-openssl\lib -DOPENSSL_INCLUDE_DIR=C:\Users\Wo
lf\Desktop\vc-openssl\include -G "Visual Studio 11"
CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDet
ermineCompilerId.cmake:446 (execute_process):
execute_process given COMMAND argument with no value.
Call Stack (most recent call first):
C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompile
rId.cmake:48 (CMAKE_DETERMINE_COMPILER_ID_VENDOR)
C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCCompil
er.cmake:131 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:1 (project)
-- The C compiler identification is unknown
CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDet
ermineCompilerId.cmake:446 (execute_process):
execute_process given COMMAND argument with no value.
Call Stack (most recent call first):
C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCompile
rId.cmake:48 (CMAKE_DETERMINE_COMPILER_ID_VENDOR)
C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeDetermineCXXComp
iler.cmake:127 (CMAKE_DETERMINE_COMPILER_ID)
CMakeLists.txt:1 (project)
-- The CXX compiler identification is unknown
-- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the sys
tem variable OPENSSL_ROOT_DIR (missing: OPENSSL_LIBRARIES) (found version "1.0.
1e")
-- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the sys
tem variable OPENSSL_ROOT_DIR (missing: OPENSSL_LIBRARIES) (found version "1.0.
1e")
statusCompiling on WIN32
CMake Error at bitshares/CMakeLists.txt:50 (add_subdirectory):
add_subdirectory given source "vendor/leveldb-win" which is not an existing
directory.
-- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the sys
tem variable OPENSSL_ROOT_DIR (missing: OPENSSL_LIBRARIES) (found version "1.0.
1e")
** for a debug build: cmake -DCMAKE_BUILD_TYPE=Debug ..
CMake Error: The following variables are used in this project, but they are set
to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake file
s:
LIB_EAY (ADVANCED)
linked by target "gw_miner" in directory C:/Users/Wolf/Desktop/coyote_miner
linked by target "gw_miner" in directory C:/Users/Wolf/Desktop/coyote_miner
linked by target "pool_miner" in directory C:/Users/Wolf/Desktop/coyote_mine
r
linked by target "pool_miner" in directory C:/Users/Wolf/Desktop/coyote_mine
r
linked by target "pool_server" in directory C:/Users/Wolf/Desktop/coyote_min
er
linked by target "pool_server" in directory C:/Users/Wolf/Desktop/coyote_min
er
linked by target "blockchain_tests" in directory C:/Users/Wolf/Desktop/coyot
e_miner/bitshares/tests
linked by target "momentum_pow_test" in directory C:/Users/Wolf/Desktop/coyo
te_miner/bitshares/tests
linked by target "timekeeper" in directory C:/Users/Wolf/Desktop/coyote_mine
r/bitshares/tests
SSL_EAY (ADVANCED)
linked by target "gw_miner" in directory C:/Users/Wolf/Desktop/coyote_miner
linked by target "gw_miner" in directory C:/Users/Wolf/Desktop/coyote_miner
linked by target "pool_miner" in directory C:/Users/Wolf/Desktop/coyote_mine
r
linked by target "pool_miner" in directory C:/Users/Wolf/Desktop/coyote_mine
r
linked by target "pool_server" in directory C:/Users/Wolf/Desktop/coyote_min
er
linked by target "pool_server" in directory C:/Users/Wolf/Desktop/coyote_min
er
linked by target "blockchain_tests" in directory C:/Users/Wolf/Desktop/coyot
e_miner/bitshares/tests
linked by target "momentum_pow_test" in directory C:/Users/Wolf/Desktop/coyo
te_miner/bitshares/tests
linked by target "timekeeper" in directory C:/Users/Wolf/Desktop/coyote_mine
r/bitshares/tests
-- Configuring incomplete, errors occurred!
See also "C:/Users/Wolf/Desktop/coyote_miner/CMakeFiles/CMakeOutput.log".
See also "C:/Users/Wolf/Desktop/coyote_miner/CMakeFiles/CMakeError.log".
-
can you add the proxy support in this software?
-
Can anyone provide info on how to setup this with solo mining?
Launch your
ProtoSHares-Qt.exe -server -rpcuser=user -rpcpassword=pass
./gw_miner.exe localhost user pass
Ok that didn't help me. How do I get this thing to mine at all? I can only start the bench mark and that is useless. I'm a noob and geek illiterate, please make it simple. I'm using win8 64 bit version i5 cpu I want to solo mine.
-
Have an error compile pool_miner with latest cmake and libboost 1.55
Text of error here http://pastie.org/8643886
Looks like that issue https://github.com/InvictusInnovations/coyote_miner/issues/2
Someone could help with that?
-
Run refused...
How to set this miner?
I created a *bat file with only "gw_miner.exe 162.243.67.4 Pj3XYFCXofPzYTAMfpH9LU2uYpSz4hdeBA", and got this
(http://i.imgur.com/0VPA8y0.jpg?1)
i tried pts.rpool.net:2336, but the same story against of ptsminer 0.7 works with wallet address and number of threads inserted in bat
-
Run refused...
How to set this miner?
I created a *bat file with only "gw_miner.exe 162.243.67.4 Pj3XYFCXofPzYTAMfpH9LU2uYpSz4hdeBA", and got this
(http://i.imgur.com/0VPA8y0.jpg?1)
i tried pts.rpool.net:2336, but the same story against of ptsminer 0.7 works with wallet address and number of threads inserted in bat
This miner is for solo-mining
Example usage
gw_miner.exe <local_IP> <RPC_Username> <RPC_Password>