Quote from: oliwer21 on September 17, 2017, 07:24:51 AM

Quote from: 616westwarmoth on September 17, 2017, 05:19:54 AM

Quote from: oliwer21 on September 17, 2017, 05:13:06 AM

Quote from: emdes on September 17, 2017, 02:18:30 AM

Quote from: bible_pay on September 17, 2017, 01:46:10 AM

Quote from: emdes on September 16, 2017, 11:47:35 PM

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.

"Run linux" dev said the want support small miners and now "run linux"
There was not such problem with 7000block and even ddos. Prolem is with updates, what happend so special that dev must reduce windows hash on last update? BTW even your xeon-w3503_01 have 2x my ryzen 1700X (80% cpu usage, 37ghz all core) hasrate2... do you think it normal. Where all work from my cpu goes?
i don't want unpolite but miner vultr_debian4 is now in top 10 since 2-3 days, before never... who's this machine?(simple answer).
"We have an incredibly responsive Dev" Yes, for linux. They ignore ALL questions for past 3-4 days from windows users about hash rate. I now that bible_pay is running linux and he dont care windows...
BTW im not angry... i want just get atention of devs to get answers for questions that i make and other windows users. I only want to get through their "ignorance wall" ;P
P.S. Do You know why some users(on laderborad) have 8k HPS and 38k HPS2 and other with 36K HPS get also 38 HPS2?

The dev is not ignoring any question nor is he purposely introducing "bugs/limitations" for windows miners. If anything, you're wrong in assuming that biblepay is a linux guy as even the pool is running on windows.

The f7000 algorithm modification has been extensively talked about the past few weeks including why it was/is necessary and its consequences. There was major issues when it went live so our dev was busy dealing with all of that and I think he did an admirable job in dealing with that chaos. He was also busy fixing the pool and dealing with DDOS attacks so that you could still keep mining using it.

Finally, performance is something difficult to understand as there are so many factors affecting it; from your CPU, memory, disks, internet connectivity to w/e is running on your machine and could interfere with the mining software) and we're talking about a brand new algorithm on top of that! It could even only be an issue with how the hashrate is calculated VS your actual performances.

The performance issue on windows has only been there for a few days and Robert (biblepay) said that he is now looking into it. It might take a long time as troubleshooting performance issues on a specific platform is not an easy task.