05:44:23 <sech1> poolin was 27 MH/s, it already dropped to 2.6 MH/s
05:44:49 <sech1> This hashrate didn't resurface anywhere else, so network slowed down a bit
05:45:03 <sech1> Estimated fork time: 2019-11-30 20:06:17 CET
06:30:41 <sech1> https://blog.genesis-mining.com/moneros-randomx-algorithm-fork-and-its-aftermath
06:45:30 <jtgrassie> ^ and https://blog.genesis-mining.com/the-big-controversy-what-is-asic-resistance
06:45:43 <jtgrassie> LOL
06:46:21 <jtgrassie> Too much voice given to people that don't understand hardware.
08:52:16 <tevador> cloud mining is a big scam anyways
08:56:23 <tevador> lol, RandomXmas
08:57:48 <sech1> Someone needs to decorate Christmas tree with ARM boards and mine RandomX on them
09:31:29 <Inge-> I'm dreaming of a hot christmas
09:33:33 <Inge-> sech1: I managed to get 6KH on a dual E5-2670 with randomx-benchmark by running 2 instances and using cpu affinity. But not managed to get xmrig quite there - 5800H/s max - and that just by letting it managing NUMA
09:33:37 <Inge-> any tips?
10:36:01 <wow-discord> <sech1> Probably post it in xmrig github, it clearly doesn't pick up NUMA layout properly
10:50:00 <tevador> looks like I found the first false positive with RandomX Sniffer
10:50:03 <tevador> Process AcroRd32.exe (PID 12052) may be mining RandomX on 3 thread(s)
10:50:22 <cohcho> What's it?
10:50:54 <tevador> Acrobat Reader
10:51:07 <cohcho> found on the internet; I'm happy that are false positives
10:53:30 <tevador> it's time to improve the heuristic
11:19:56 <tevador> apparently, Acrobat Reader uses round to -infinity mode
11:20:04 <Inge-> sech1: so in principle, I should not need to mess with affinity / numa with XMRIG ? It should make correct number of threads and split correctly? (e.g. in this case 10 threads on each 8/16 core/thread cpu)
11:21:58 <wow-discord> <sech1> Try to go with auto-config (delete all threads from your config)
11:39:02 <Inge-> First time I tried, I didn't have any thread config, and got about 5700 H/s - but now that I was double-checking with no settings, it correctly detects 2 numa nodes, total L2 and L3 cache, allocates 2 sets of huge pages etc - and yields 6300 H/s - which is better than I got from randomx-benchmark
12:39:04 <tevador> https://github.com/tevador/randomx-sniffer/releases/tag/v0.0.2
12:48:46 <hyc> funny how genesis mining blog is like everyone else, misreporting Monero's approach to PoW
15:07:16 <needmonero90> Ooo the sniffer looks cool
15:10:57 <hyc> here's what keeps supercomputers too busy to mine https://mobile.twitter.com/bencbartlett/status/1200515462473191425
17:11:15 <sgp_> Can anyone join the coffee chat today at 18 utc? (<1 hr)? PM me if you want to participate in the live discussion
18:13:29 <sech1> last 100 blocks are all v12 now
18:13:56 <sech1> I mean v11.12
18:57:59 <tevador> IT'S HERE
19:05:08 <midipoet> fair play to all involved. serious achievment indeed.
19:05:38 <randomXcellence> seriously
19:07:30 <moneromooo> Thanks tevador and sech1 :)
19:08:24 <randomXcellence> Tevador!!!!
19:13:47 <kinghat> congrats guys!🥳
19:16:02 <gingeropolous> didn't poolin stop mining?
19:16:20 <sech1> yes, they stopped
19:17:12 <gingeropolous> they got a randomx block apparnetly
19:17:12 <sech1> or announced that they would stop, I see they've found a block
19:19:19 <sech1> Nicehash, not so impressive yet: https://www.nicehash.com/my/marketplace/RANDOMXMONERO
19:19:23 <tevador> must have been a lucky block
19:22:23 <sech1> All pools are still sub 300 MH/s combined, I expected more by now
19:23:26 <tevador> this is just the initial drop due to unupdated miners
19:23:41 <tevador> should be >500 MH/s tomorrow
19:24:00 <sech1> 304.65 MH/s on pools now
19:25:40 <hyc> yeah looks like still a drop in hashratd
19:26:29 <sech1> ok, so next to keep an eye on is 1980481, right?
19:26:35 <sech1> epoch change
19:35:23 <gingeropolous> hrmmm indeed
19:36:38 <midipoet> explain the epoch change please?
19:36:40 <nioc> thank you tevador sech1 and hyc
19:36:55 <sech1> midipoet Dataset update, happens every 2048 blocks
19:37:12 <midipoet> how do you mean dataset y
19:37:15 <sech1> should be smooth, miners will just stop for a few seconds to update dataset
19:37:21 <sech1> 2 GB RandomX dataset I mean
19:37:36 <midipoet> ah i understand, the calculations from which difficulty is comprised, and such
19:37:43 <midipoet> right?
19:37:54 <sech1> No, it's like DAG in ETHash
19:40:14 <midipoet> had to google the DAG in ethash. it basically helps ensure the algo is memory-hard
19:41:12 <sech1> yes, big chunk of memory to randomly read from during hash calculation
19:52:22 <tevador> https://ragerx.lol/
19:52:23 <tevador> wtf
19:53:48 <gingeropolous> its prolly an OS that has all the optimizaitons preconfigured
19:54:21 <gingeropolous> like those crazy intel speedups that the one guy on here did
19:55:11 <tevador> closed source
19:55:45 <gingeropolous> bound to happen
19:55:53 <sech1> 3.5% fee pool
19:55:56 <sech1> from ryo devs
19:56:05 <sech1> Why am I not surprised?
19:56:48 <tevador> ryo is in the final agony before death
19:57:00 <tevador> I guess
19:57:03 <sech1> XMRig 10% slower, of course we can believe these numbers, right?
19:57:48 <tevador> it's just like when Intel publishes their own benchmarks
19:57:57 <tevador> except they at least put an asterisk there
20:00:06 <sech1> oh, actually their numbers show 14% faster
20:00:16 <sech1> no realistic at all
20:00:53 <sech1> ah, they reduced XMRig by 5% because of 5% default dev fee lol
20:01:06 <sech1> xmr-stak-rx with exactly the same code if 5% "faster"
20:01:08 <sech1> *is
20:01:47 <sech1> 4.83/4.46 = 8.3%, this is more realistic on server Xeons
20:02:02 <sech1> actually, it's achievable
20:02:20 <sech1> I wonder if they're just bluffing or discovered the same optimization as I did
20:03:18 <tevador> they are talking about OS optimizations, so I'd say the miner code is copied from XMRig
20:03:20 <sech1> but 8% on new Ryzens - no, impossible
20:03:35 <sech1> No OS optimizations can give this boost
20:03:45 <sech1> unless it's silently overclocking CPU
20:04:10 <tevador> disabled prefetch can give ~5%
20:04:38 <tevador> that can theoretically be done by a kernel driver
20:05:00 <sech1> it can be done in BIOS
20:05:00 <tevador> but it's very CPU arch specific
20:05:23 <tevador> it can be done even if the BIOS doesn't have the option
20:05:52 <sech1> not for Ryzens
20:06:42 <tevador> BIOS doesn't do anything but set a MSR value you tell it to set
20:07:34 <sech1> hmm, AGESA 1.0.0.4B BIOS is out for my MB
20:07:47 <sech1> I'll check if it has something interesting inside
20:10:51 <sech1> I heard it has some prefetcher options, let's see... Flashing new BIOS now.
20:12:11 <sech1> but this ragerx, lol
20:12:34 <sech1> They have their own pool, you can't change it, so they can fake hashrates both in the miner and on the pool
20:14:25 <tevador> I wouldn't be surprised if they paid only in Ryo
20:18:09 <Svaaag> override pool url in dns to your own
20:19:04 <tevador> that violates their DRM
20:19:07 <tevador> j/k
20:19:08 <sech1> Nope, can't find prefetcher options in new BIOS
20:19:45 <tevador> sech1: which MB?
20:21:19 <sech1> Asus Prime B450M-K
20:21:35 <p3rL> .network
20:21:55 <sech1> hashrate didn't change either with new BIOS
20:22:16 <tevador> so I guess Asus doesn't offer this option
20:22:41 <tevador> it's a niche setting, most people won't use it
20:47:40 <cohcho> "BIOS doesn't do anything but set a MSR value you tell it to set" Can you prove it?
22:37:02 <kico> how to config xmrig to use dual cpu ? on windows ...
22:37:18 <kico> it only uses 1 cpu by default
22:46:53 <Inge-> sech1: is your optimization in current xmrig?
22:47:31 <sech1> not yet
22:48:26 <Inge-> I am still pretty surprised that I am getting 5% more with xmrig on dual E5-2670 after the fork, compared with earlier benchmarks, while Ryzen is spot on identical
22:49:01 <Inge-> kico: on Linux it seems to automatically do the right thing
22:49:05 <moneromooo> Is it moving a substantial fraction of c ?
22:50:07 <kico> Inge-, I see in windows I'm having a hard time to detect 2nd cpu
22:50:16 <kico> tried fidling with threads
22:50:30 <kico> numa field in config is only true/false it seems
22:51:36 <Inge-> what does xmrig say when starting up?
22:54:31 <kico> Inge-, https://i.imgur.com/QsxPHeh.png
22:54:41 <kico> it says numa 2
22:54:45 <kico> just noticed
22:54:52 <kico> but cpu load is 50%
22:56:20 <Inge-> my dual cpu system also has 50% cpu load
22:56:41 <Inge-> as there is not enough cache for running an RX thread on each CPU thread
22:56:54 <kico> oh ok makes sense
22:57:05 <kico> maybe that's as much as its going to make
22:57:14 <kico> I should try linux anyways
22:57:47 <kico> about 3kh on dual intel hexacore
22:58:32 <Inge-> I'm guessing it is using 12 threads?
22:58:36 <Inge-> if you press h for hashrate
22:58:36 <kico> x5650
22:58:42 <kico> yeah
22:59:02 <Inge-> so that is the max, based on your cache. It correctly allocates for 2 NUMA nodes
22:59:03 <kico> 12t tried 24 but was worst
22:59:11 <Inge-> what hashrate you do you get per thread, approximately?
22:59:17 <kico> ok thanks a bunch Inge-
22:59:33 <kico> ~240h/s
22:59:38 <kico> per thread
23:00:12 <Inge-> my E5-2670 gets about 400 H/s per thread
23:00:27 <Inge-> so 240 doesn't seem too unreasonable
23:00:45 <kico> yeah maybe that's it for this cpu hehehe
23:00:53 <kico> I will try linux just in case
23:01:21 <Inge-> you can also google randomx benchmarks - there are some similar cpu systems in one of the lists
23:01:52 <kico> great thanks a bunch for the help Inge- :)
23:02:01 <Inge-> no worries.
23:02:29 <kico> this is the "oficial" for benchmarks no ? https://i.imgur.com/QsxPHeh.png
23:02:31 <kico> ops
23:02:36 <kico> https://monerobenchmarks.info/
23:03:24 <kico> seems legit
23:03:32 <kico> DUAL XEON X5650	2743	300 W
23:03:42 <kico> mine is doing 2900
23:03:47 <kico> should be it :)
23:03:51 <kico> thanks!
23:05:18 <rottensox> kico: <3
23:05:35 <kico> rawttensox
23:05:38 <kico> heyo
23:06:06 <Inge-> kico: yeah, I think you are fine.
23:06:29 <kico> cheers :)
23:35:40 <cohcho> gingeropolous: have you used --enable-randomx for xmrchain.net monerod?
23:36:17 <cohcho> for monero-blockchain-explorer behined xmrchain.net*
23:37:01 <needmonero90> Hashrate is half a gigameg now
23:40:55 <cohcho> sech1: You may add "RandomX ASIC" into coinbase signature for your solo miner.