I don't care about the lower hashrate/payouts, but it's not really "fair" when linux get 2x hashrate on the same hardware. Just wanted to know why

Guys- Its not getting ignored- we were moving like a steamroller until F7000 hit, and the issue is things have to be prioritized.
Its a higher priority to address Prod issues than "hashrate" issues.
Now it appears the pool is running again without issues so now I can take a look at the hash rate issues across OS.
The pool is storing the OS flavor per miner now, so I should be able to go in and write a report of average speed per OS flavor.
I do see that windows appears to hash at a much slower rate than linux for some reason.
Im seeing 34,000 HPS on my vultr-debian vs 4,000 on my dual CPU xeon windows web server. Quite a disparity there. Definitely unintentional from our engineering standpoint.
Yeah im not asking you to magically fix it over night, just look into it. Thanks

For me it sounds like magic cuz they compile against ddos and what we have got? SAME cpu usage but HALF of hash rate2. And it was only wallet upgrade...
And first devs answer was "7000k"?!?!?
Reall!?! Problem devs created 8 HOURS ago not 8 DAYS.
I get you are angry but compare this coin against other small coins. We have an incredibly responsive Dev. Block 7000 screwed a LOT of things up. It was a major change to the algo. So to fix it, core pieces of the software have to change. This might change hash rates. This is still a very new coin, I'm positive the Dev is looking into it. There have been significant DDOS attacks occurring on this coin and the primary focus of the Dev has been to protect the pool, which is how a lot of newer users mine (and how many people prefer to mine). So he has not had unlimited free time to fix this issue.
In the meantime, you have several options. One, run Linux, which seems to be doing better than Windows on the issue. Two, accept the lower hash rate and live with it until the fix is in, knowing MOST users are doing the same so we're all losing a similar hash rate. Three, give up on BBP, take your CPU somewhere else and come back next year if you want when the bugs are hopefully all worked out. Four, fix the problem and upload the solution to Github.