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 - gigawatt

Pages: [1] 2
1
Introducing xptMiner-PTS-5k, the only open source miner optimized specifically for Radeon 5 and 6 series GPUs!

What do I mean by optimized?  Well, my aging Radeon HD5830 mines at ~800 collisions/minute with only minimal overclocking:


This miner works on both YPool and 1GH, simply specify the correct pool url with the "-o" option:
YPool: -o ypool.net:8080 -u username.workername -p pass
1GH: -o ptspool.1gh.com:18120 -u 1PTSADDRESS -p anything

Windows Binaries: (both 32 and 64-bit builds)
Mega.co.nz
Dropbox (mirror)

Linux Users:
You can download the source code from the project's GitHub page: https://github.com/llamasoft/xptminer-pts-5k
A compile guide is also available from the project's main page.  It assumes you already have the AMD APP SDK installed.
For Ubuntu and BAMT users, the compile process simple:
Code: [Select]
sudo apt-get -y install build-essential m4 openssl libssl-dev git libjson0 libjson0-dev libcurl4-openssl-dev
git clone https://github.com/llamasoft/xptMiner-PTS-5k.git
cd xptMiner-PTS-5k
make

This miner has been tested on Windows 7, Ubuntu 13.10, and BAMT.


Performance Tuning:
It is highly recommended that you install the latest Catalyst drivers for your GPU.
If you are on Linux, please update to the latest AMD APP SDK.
Once your software has been updated you can tune the performance of the miner by adjusting the "-b" flag (default value is 23).
If your GPU has 1GB of RAM, an initial value of -b 23 is recommended.
If your GPU has 2GB of RAM, an initial value of -b 24 is recommended.
Try increasing or decreasing the value for "-b" until you find the best performance for your GPU and software configuration.


Benchmarks:
Want your GPU included in the list?  Post a screenshot of your miner along with the following information:
  • Collisions/Minute
  • GPU model
  • GPU clock settings
  • Mining parameters
Collisions/MinuteUserGPUClock SettingsParameters
======================================================================
~800 cpmGigawattRadeon HD5830Core: 900MHz, Mem: 1000-b 23 -s 0

2
Sweet!  Looks like my pull request got merged.  :D
https://github.com/super3/invictus.io/pull/50

3
I've submitted a few typo and standardization suggestions: https://github.com/super3/invictus.io/pull/50

  • bitshares-pts.php - It kept alternating between "ProtoShares", "Protoshares" and "protoshares" where the rest of the site just used "Protoshares".  Fixed capitalization of "Bitshares". Added missing period
  • bitshares-ags.php - Typo: "donators" -> "donors".  Standardized capitalization of "Bitshares".
  • funding-philosophy.php - I don't think "minable" is a word and "mineable" look odd, so I changed "is minable" to "can be mined".  Typo: too many "n"s in "technology".  Fixed capitalization of "Website" to be consistent.
  • keyhotee.php - "unstability" isn't a word, but "instability" is.


Suggestions: make a guideline of what capitalization to use for "Protoshares".  Also, from an HTML perspective, I saw "<br>", "<br/>", and "<br />" all used in the code.

My PTS address is Pstkk1gZCxc4GEwS1eBAykYwVmcubU1P8L
Send whatever you think is appropriate.



edit: Site footer had an HTML typo.  It used "&ampl;" instead of "&amp;" in a URL.  Also, for consistency, if you're going to spell out "Incorporated" in the address, you can probably afford to spell out "Drive" as well.  ;D



edit2: You guys should totally add a favicon.ico file!  The tab looks so bland without it.

4
BitShares PTS / Re: Question about selling/trading GPU code
« on: January 21, 2014, 10:52:56 pm »
Go with the fee, but yourcode need to be really good, look at reorders miner (1gh), best one OpenCL.

Any stats?

I never got the actual "mining" aspect working, so I don't have a collisions/min value to compare.  I did notice that some of the open source implementations of a GPU miner used a version of SHA512 derived from JohnTheRipper.  I did manage to get my code about 1.4x the speed of the JTR implementation.

5
BitShares PTS / Question about selling/trading GPU code
« on: January 21, 2014, 09:44:57 pm »
A while back I was working on making an OpenCL implementation of a miner for Protoshares.
I ended up writing very optimized version of the hashing code itself, but never managed to integrate it into a functioning miner.  All the code and comments I've written are from scratch.

Would I be in the wrong to sell/trade the OpenCL code?  What about giving it away freely with a donation sharing stipulation?

6
BitShares PTS / Re: Pywallet can't work with PTS wallet.dat
« on: January 21, 2014, 09:33:57 pm »
What are you trying to accomplish?  If you just want to dump your keys from your wallet, you can copy/paste the wallet.dat file into the .protoshares directory and run Protoshare-QT normally.

7
Any ideas?

Code: [Select]
[  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.

8
Any ideas?

Code: [Select]
[  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

9
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.

10
120 HPM?  What does that boil down to in HPM per CPU GHz?  (e.g. Dual Core 3.2 GHz = 120 / 6.4)

11
BitShares PTS / Re: Corrupted wallet.dat
« on: November 12, 2013, 11:55:10 pm »
That really sucks :(
Private key export was also broken with the first version on git... so I didn't do it.
Any other way to extract the private key manually from wallet.dat, if I know the address?

Private key export worked fine.  It was private key import that was broken (it was looking for the wrong version bytes).

You might be able to use something like pywallet to extract your keys from it.

12
BitShares PTS / Re: 1 BTC Bounty - Build Faster Miners People :)
« on: November 12, 2013, 10:03:59 pm »
I dunno who I should pester about this small tweak, but...

Given that even on a massive system, the collisionspermin metric is < 100, maybe this "hashmeter" line should be adjusted.

I think regular units would be fine here.  hashpermin is already a small number, so hashpersec would be tiny, khashpersec is unreadable.
printf("hashmeter %.6f hash/s\n", dHashesPerSec);

13
BitShares PTS / Re: 1 BTC Bounty - Build Faster Miners People :)
« on: November 12, 2013, 09:05:20 pm »

Agree, better is optimized standalone miner which can mine at pool and solo using getwork/getworktemplate from the wallet.

How about we go with the lowest common denominator: optimize the momentum_search function.
If you're doing anything with ProtoShares, it depends directly on momentum_search.  If you're optimizing anything else, it's application-specific.

14
BitShares PTS / Re: 1 BTC Bounty - Build Faster Miners People :)
« on: November 12, 2013, 08:38:50 pm »
Made a few more tweaks.



Averaging ~6 cpm per GHz.

15
BitShares PTS / Re: 1 BTC Bounty - Build Faster Miners People :)
« on: November 12, 2013, 06:53:29 pm »
I'm testing on a 2.0 GHz single core VPN.
So yeah.  I'm doing pretty well I'd say.


The default setup is ~2 collisions/min and requires 50% more memory.

Pages: [1] 2