a10-5800k -t 2
but i think need more time to test....
I too had slightly worse performance on my AMD processor, but my Intel desktop did see an improvement. I'm thinking it may have something to do with jh00's version including profiling. Also, how come your binary is so large? Even the stock build is ~200k. |
|
|
|
I took the time to finally get xptMiner to compile with GCC for Windows. It was a nightmare for me, but what does that mean for you? Christmas may have come early. I've compiled my optimized code for each of the following architectures: generic, core2, corei7, corei7-avx, k8, k8-sse3, and barcelona (k10). The Windows x64 binaries are available from here:https://mega.co.nz/#F!YsZSHYKA!IC8LK_MBGwqC-gWOpO7zoQhttps://www.dropbox.com/sh/wtxvxvkirxax2vj/9P_Rxb9V1y (dropbox mirror) Use whichever corresponds to your processor architecture. If you're unsure, here's a quick guide based on your CPU manufacturer and age: Intel: [Older] core2 -> corei7 -> corei7-avx [Newer] AMD: [Older] k8 -> k8-sse3 -> barcelona (k10) [Newer] Worst case scenario, use generic. I will not be releasing any 32-bit builds. "High performance 32-bit" is an oxymoron. Let me know what sort of improvements you see! Some builds may be slightly slower than the stock jh00 miner. It all depends on your CPU. |
|
|
|
I have only waited a few minutes, but I am not really seeing any improvement on my 20 computers mining this coin with the new miner. Is it optimized for a particular processor? 16 of my systems are dual processor E5420's, one is a hex core newer xeon, an 8 core bulldoser, an i5 (ivy), and lastly an i7 (ivy).
Wow... uh... if you're running on that many different platforms, I'd actually recommend that you compile your own for each using architecture-specific optimizations. There's not a "one binary fits all" kinda thing. |
|
|
|
Aww hey now, you could have left part of my dev fee in there. I did come up with the improvements ya know.  Resolved. Thank you Chida! |
|
|
|
I'm clocking in at 692 kHash/s on a c1.xlarge Amazon AWS instances.
For reference, that averages out to about 40 shares/hour on yPool. |
|
|
|
you forget to mention 2.5% fee right?  Ok fine, it's a (1.25 * 0.975 = ~21.8%) improvement.  I'm clocking in at 692 kHash/s on a c1.xlarge Amazon AWS instances. |
|
|
|
|
I'm not sure if it's a fluke or what, but the Amsterdam 2 servers seem to be ~15% faster than the New York 2 servers.
I wonder if it's congestion?
|
|
|
|
Nope, read the comments. // The first (80 - 4) bytes will be the same each time, so pre-calculate
// the state after feeding 76 bytes. The last 4 bytes is the nonce.
sph_keccak512_context ctx_keccak_init;
sph_keccak512_init(&ctx_keccak_init);
sph_keccak512(&ctx_keccak_init, &block->version, 80 - 4);
The first 76 bytes of input are the same, so we keep the hash state after feeding it those bytes. Then, on each pass we "restore" that state, feed it the last 4 bytes (the nonce), then calculate the rest of the hash. So instead of feeding it 80 bytes each pass, we only feed it 4. Here's the data structure of "block", so it should make more sense: typedef struct
{
// block data (order and memory layout is important)
uint32 version;
uint8 prevBlockHash[32];
uint8 merkleRoot[32];
uint32 nTime;
uint32 nBits;
uint32 nonce;
// remaining data
uint32 uniqueMerkleSeed;
uint32 height;
uint8 merkleRootOriginal[32]; // used to identify work
uint8 target[32];
uint8 targetShare[32];
}minerMetiscoinBlock_t;
The first 76 bytes correspond to version, prevBlockHash, merkleRoot, nTime, and nBits. These stay the same during each pass of the hash algorithm. The last 4 bytes are the nonce, that changes each time. No point repeating work if you don't have to. |
|
|
|
|
I've made updates to the metiscoin miner, so anybody using this script should run ~/stop-miner; ~/build-metiscoin-from-git to download the latest version.
It features a 20-25% hash rate improvement over the old algorithm.
Enjoy!
|
|
|
|
8cpu/16gb VPS digital ocean 429.56 kh/s
Added to the benchmark. How long did you let it run for? I found that the speeds steadily crept upwards for about 15 minutes before leveling off. 10-15min. Now it is at 476. I get 74 kh/s for 1cpu/512MB VPS at digital ocean For comparison, that averages out to about 3.8 shares/hour on yPool. |
|
|
|
8cpu/16gb VPS digital ocean 429.56 kh/s
Added to the benchmark. How long did you let it run for? I found that the speeds steadily crept upwards for about 15 minutes before leveling off. |
|
|
|
Thanks again - tip sent.
Getting 162.82 kHash/s on 2CPU/2GB VPS at Digital Ocean Amsterdam (36 ms to pool)
Added your stats to the benchmark table. Thanks for the tip! |
|
|
|
Thank you, really helpful. If i want to add a second one?
Add a second VPS? On Digital Ocean you just create a new Droplet and paste the script into it like you did the first time. You'll use the same info that you did in the first. (You can have multiple miners pointing to the same "worker" on yPool.) |
|
|
|
Anybody have luck getting the miner output log working? On Digital Ocean it seems to be 50/50 on reboot but I haven't had it work on AWS yet. Also, I'm revising the AWS c1.xlarge number to 650 kHash/s. That's where it seemed to level out at. Comes out to about 30 shares/hour on yPool. https://i.imgur.com/vmmZFP7.png |
|
|
|
Benchmarks| User | VPS | Type | kHash/s | | ============ | ============ | ============ | ============ | | gigawatt | Digital Ocean | 1 CPU/512 MB | 101 | | TiberiuC | Digital Ocean | 1 CPU/512 MB | 74 | | steeleminer | Digital Ocean | 2 CPU/2 GB | 162 | | TiberiuC | Digital Ocean | 8 CPU/16 GB | 476 | | gigawatt | Amazon AWS | c1.medium | 186 | | gigawatt | Amazon AWS | c1.xlarge | 690 |
Want your benchmark added? Just post it in the thread and I'll update the list.
|
|
|
|
If you are looking for GPU mining, please use this instead!Setting up a Metiscoin Pool Miner on VPS for Absolute NoobsDonations welcome! BTC: 1E2egHUcLDAmcxcqZqpL18TPLx9Xj1akcV Ψ: AWHJbwoM67Ez12SHH4pH5DnJKPoMSdvLz2 MTS: MEu8jBkkVvTLwvpiPjWC9YntyDH2u5KwVy Before You Begin- Download PuTTY (putty.exe) so you can connect to your VPS when the time comes.
- Sign up for a DigitalOcean or Linode account.
- During the creation process, be sure to create a node running Ubuntu 13.04 x64 (not x86)
- Pick whichever hardware configuration you like (number of CPUs, RAM, etc)
- If you signed up for DigitalOcean, check your email for your root password. If you signed up for Linode, your password will be what you specified.
- Run PuTTY and paste the node's IP address into the "Host Name" slot, then hit "Open" at the bottom. (figure 1)
- PuTTY will ask you to confirm the SSH key, press Yes (it will only ask once) (figure 2)
- Type or paste your password into PuTTY and press enter. To paste, simply right click.
- Note: You will not see the password characters! This is normal.
Getting Down to Business- If you chose DigitalOcean, it's time to change the root password! Type passwd, press enter, then enter a new password. Just like before, the password characters will not show up. (figure 3)
- Copy this automated setup script to notepad. (highlighted version)
- At the top of the script, there are fields starting with "YPOOL_". Fill these out with your desired info. Be sure to keep the quotes!
- YPOOL_WORKER is your yPool worker name. YPOOL_WORKERPASS is your yPool worker password.
- Copy the entire modified script from notepad and paste it into your PuTTY window (right click), then hit enter.
- The setup is now running. It will take approximately 3 minutes to complete.
- Once the script completes, you will see a brief help message and list of commands. (figure 4)
Congratulations! You're now mining for metiscoins! If you'd like to maximize your mining potential, please see my mini-guide on How to Clone DigitalOcean Droplets. Changelog- 24 January, 2014 - Miner code updated. Now with 20% more turbo! Run ~/stop-miner; ~/build-metiscoin-from-git to download the latest version.
- 22 January, 2014 - Fixed apt-get list, number of threads determined by /proc/cpuinfo.
- 22 January, 2014 - Initial release.
NotesThe images in this guide are from my other primecoin guide and are slightly dated. The images serve to illustrate, but shouldn't be taken as definitive. Known IssuesThere's a known bug with this miner where redirecting output to file may or may not not work! Because of this, mining speeds may not appear when using ~/peek. If you want to verify your miner is working, check the process listing for CPU usage or run the miner command manually. Alternately, sometimes a reboot helps. /usr/local/bin/xpt -o ypool.net -u user.worker -p xIf you have any questions or comments, feel free to speak up.
|
|
|
|
|
Right now I'm playing with an AWS c1.medium instance and getting ~130 kHash/s. It's a 2 CPU instance if that's of any help.
(Updated top post and script with donation address.)
|
|
|
|
It's that time again! I've released another "Noobproof VPS Mining Guide", this time for Metiscoin! For your hardcore individuals: it's compatible with Amazon AWS but will work on almost any VPS virtualization platform. https://bitcointalk.org/index.php?topic=427516 |
|
|
|
|
Show Posts
