I've made a research on the commit that the NoodleDoodle has claimed to make publicly available. And you know what, I have found something very weird.
Experiment
Core I5, Windows.
Two attempts
1) Binaries compiled from the source code that NoodleDoodle committed yesterday.
2) Pre-compiled binaries that were spread on this topic.
Results
Hashrate:
1) Compiled binaries: 8.3 - 8.9 hr/s
2) Pre-compiled binaries: 15.1 - 15.5 hr/s
Come on guys, this stinks! Aren't you lying again?
My questions:
1) How exactly can the hash rates differ by the factor of 2 if they are on the same code? (Hint: it is impossible).
2) Why do the "team" claim that they've made the source code publicly available when they actually hide the real optimization?
3) Doesn't this mean that instamine is actually going on?
4) How much more the "team's" miners are optimized?
I guess, explanation is required.
Everyone is welcome to try it out themselves.
With the Bytecoin reference code and original build put out, Windows was roughly 2-3x slower than Linux. Noodle doubled Windows hashrates twice. The first time was with compiler optimization and affected Windows only. The second time was the loop change (now incorporated) and that doubled both Linux and Windows hashrates. From IRC:
14:57 NoodleDoodle: No, the first one is compiler "optimization" and the second one is the commit.
14:58 equipoise: which compiller are you using? I tried with intel
14:59 equipoise: compilling with avx
15:00 NoodleDoodle: You don't need avx.
15:00 NoodleDoodle: Just sse3.