What miner are you using? I get 265 H/s from an i7 3770 using Wolf's miner with threads=1/2 of cores (physical or virtual if it has HT). Having AES-NI is a plus as well as running on Linux instead of Windows. But that's just what gets me the best results. Xeons seem to be different to tweak than desktop CPUs. And no, you're fairly limited unless you have a lot of CPUs to work with.

Here's a somewhat useful chart: https://docs.google.com/spreadsheets/d/1MI-ic0Os25hgGUImW54sUIjZY_pUNQNa_W8Se5pRGBs/edit?pli=1#gid=0

I've been mining Monero on my CPUs for a little over a month (right about the time difficulty jumped up) and my CPUs are still turning a profit.

I think that minerd-wolf-07-09-14 is only for non-AES-NI cpus. That would explain the drop in hashrate for you and why when I tried it at first I saw a major drop in speed.

What OS are you using? On my 50+ Ubuntu and Windows 7 machines, the memory hasn't leaked and they've been running for 5+ days straight.

Edit: I'm a fool.

I personally haven't tried it, but I think this is what you might want to look into: https://bitcointalk.org/index.php?topic=558715.0

Well I guess my calculations were off and instead of 20MH/s I'm getting 44MH/s. I'm getting about 9.5X the hashrate (isn't 4X the average?)on X11 over scrypt. Thanks again PW

Thanks PW! Just pointed 20MH/s X11 at the test pool.

Have you noticed your hashrate bouncing around and averaging to a lower than normal hashrate, or is it fairly consistent around 9.25 MH/s? I ask because I noticed that my hashrate now bounces around from 1.5 to 7.5 MH/s whereas it used to always be within a tighter range of 5-7 MH/s.

After over 24 hours mining on the new stratum server, I have <1% rejects down from 6%, but my average hashrate has dropped 17%! I went from an average of 6MH/s before, to 5MH/s over the last 30 hours. At first I thought it was just variance, but it seems to be consistently staying lower. No config has changed on my end. Any clues what could cause such a dramatic change/loss in hashrate?

The "ignore" button works almost as well. And it is wonderful!

I now realize that the cpuminer does support stratum and I was using it and not realizing it. I will verify the latency to the various servers to make sure I didn't miss something. I did wipe my VPS before reconfiguring for MC, so maybe I made a mistake earlier and couldn't find it. I hope to get this sorted out and mining back at Waffle soon. Thanks!

I really don't know how I missed that after all this time. I have actually ran some instances of it without the stratum proxy and it worked and I never even put that together. Most mining pools still have instructions in the "Getting Started" or FAQ sections saying that minerd (pooler cpuminer) doesn't support stratum and that you should go get the stratum proxy. I've been mining for 2.5 years and feel like a fool to have not noticed that and just believed all those instructions because it was stated over and over. But yes, I see at the source that it does support it. Thanks for clearing that up for me.

As for the pinging, I was getting < 20ms from cpu to stratum proxy, 12ms to VPS, and 17ms to Wafflepool. I thought that it would be low enough, but maybe not?

I'm using minerd miners (no default stratum support) connected to a central stratum proxy. That stratum proxy connects to a headless linux VPS forwarding all traffic to whatever pool I choose. All I did was change the IP on the VPS to point to Middlecoin instead of Wafflepool and all of my rejects went away. So something else is going on, because my miner configurations haven't changed at all since I started mining LTC a year ago. I guess I was just having connection issues to just Wafflepool.

I'd like to add that I was completely wrong about my issues. I thought it was my slow CPU miners, but it can't be because as everyone else said, the diff should have just increased variance, but I switched to Middlecoin (which is locked at 1024 diff) and I'm getting no REJECTED shares. So sorry for that confusion, but I only seem to have this problem on Wafflepool, which is too bad. I've tried multiple Wafflepool servers, but just get continuous REJECTED shares. I'll keep trying, I really want to mine here. Thanks to all for the information and suggestions.

This is similar to what I'm seeing. Even with 100 cpu miners, I maybe get in 1 share every 2 blocks and all the old work is rejected as the other CPUs take too much time to finish their share and then when submitting, it's too old. At least that's how I understand it works.

So it seems in the end it is a mix of the high difficulty + such a short block time on certain coins. I imagine that if Wafflepool starts mining on an altcoin with a long block time, my rejects would go away.

I was really hoping that it was the stratum proxy lagging, as I hadn't checked that before, but my tests show a 50ms delay from miner to stratum proxy to external proxy to Wafflepool. I'm not sure that that kind of delay is enough to cause this issue though. When I was mining Litecoins before I switched to this pool, I was always getting a difficulty < 200. Any time it went above 300, I started to have the issue of less accepted shares because of the time it takes the cpu to calculate such a high difficulty share. If you say CPU mining is perfectly viable at 512 share difficulty, then I'll keep working on my config to see where my setup is going wrong. I am really hoping to be able to stay at Wafflepool. Thanks for the info.

I've verified that the connection is good and the proxy is passing through traffic. If I restart my stratum_proxy and all miners pull new work, I get some ACCEPTED shares for a bit but then they slowly all turn to REJECTED which makes it seem as if my CPU miners just can't keep up with the fast block times and then just start submitting too old of work.. It is detecting the new blocks and the miners are updating correctly but I'll keep an eye on my proxy and see if there is configuration changes needed. Thanks.

Hello all, I have read through half of the posts on this thread and can't seem anything related to what I'm seeing. I only just started at this pool ~8 hours ago and everything was working well at first but now it has climbed to what seems like a 100% reject rate and am trying to figure out what on my end would cause this. I have ~100 cpu miners at 50Kh/s all working on one address as the worker (do I need to split them up?). I'm running a stratum proxy that connects to an Ubuntu server forwarding all traffic to the pool. I've checked the connection on my server and all seems good. On the stratum proxy console, I'm seeing messages like this over and over (with the Job ID changing every so often):

2014-02-24 20:37:00,700 INFO proxy jobs.submit # Submitting 9b035e96
2014-02-24 20:37:00,762 WARNING proxy getwork_listener._on_submit_failure # [62m
s] Share from '1L6Gycs8a9UhzhEsxzhiFFVA4GREtkmPkh' REJECTED: (-2, u"Job '857a' n
ot found", None)
2014-02-24 20:37:00,793 INFO proxy jobs.submit # Submitting 28f94704
2014-02-24 20:37:00,855 WARNING proxy getwork_listener._on_submit_failure # [62m
s] Share from '1L6Gycs8a9UhzhEsxzhiFFVA4GREtkmPkh' REJECTED: (-2, u"Job '857a' n
ot found", None)
2014-02-24 20:37:01,667 INFO proxy jobs.submit # Submitting 51b18119
2014-02-24 20:37:01,744 WARNING proxy getwork_listener._on_submit_failure # [62m
s] Share from '1L6Gycs8a9UhzhEsxzhiFFVA4GREtkmPkh' REJECTED: (-2, u"Job '857a' n
ot found", None)

I'm also noticing that it's detected a new block incredibly often, is this causing my CPU miners to not be able to submit even 1 share before a new block is found, causing all rejects? My hashrate is showing correctly on the site, but I'm now seeing 0 shares submitted for the last 10+ blocks. I appreciate the information and help. Thanks.

Been using give-me-ltc for a while now and I really love this new interface! Also noticed that the auto payout fee is at 0; is that going to stay or will it go back up to .001 at some point? Thanks