09:18:10 <hyc> https://mobile.twitter.com/pool2miners/status/1325277809183510529
09:18:38 <hyc> grin network 51% attack ongoing
09:19:07 <hyc> so much for asic-friendly safety
09:19:15 <sech1> weren't they shifting to asics?
09:19:35 <sech1> They should be at asic-only algorithm after almost 2 years since launch
09:20:36 <hyc> aren't they using cuckoo cycle?
09:23:51 <sech1> yes, but they have asic version which doesn't change and non-asic version which changes twice a year
12:10:45 <sech1> Zen2 vs Zen3 at different scratchpad sizes: https://paste.debian.net/1170471/
12:11:07 <sech1> Zen3 is 4.43% faster with 256 KB scratchpad where L3 doesn't matter
12:11:24 <sech1> and almost 5% slower on cn-heavy with its 4 MB scratchpad
12:12:05 <sech1> So it's +4.4% IPC on RandomX, but slow L3 cache negates it
12:55:33 <gingeropolous> why does the rest of cryptoworld think asics are fine and to be embraced?
12:55:54 <gingeropolous> in trying to find out what the current state of grin PoW is, i've stumbled on this: https://forum.grin.mw/t/grin-improvement-proposal-1-put-later-phase-outs-on-hold-and-rephrase-primary-pow-commitment/4653
13:00:08 <gingeropolous> and "It is important to note that Grin had apparently been ASIC-resistant and was only available for mining through Graphics Processing Units [GPU]. Grin executed the first hard fork in 2019 in a bid to block the possibility of mining the coin with ASICs. Before this event, the network’s algorithm supported mining with both GPUs and ASICs, but no one used ASIC mining to mine Grin." >>> https://www.tronweekly.com/mimblewimble-grin-suffe
13:00:08 <gingeropolous> ck/
13:00:33 <gingeropolous> but thats from the cryptonews sources which are rarely accurate
15:34:14 <sech1> Managed to get 6639 h/s @ 78W on 5600X (of those, 14 watts were GPU). So it would be 103 h/s/W without GPU. I could also shave off 3-4 watts by using my 2x4 GB memory. 2x16 GB uses more power. 110 h/s/W is possible.
15:34:52 <sech1> 3750 MHz @ 0.85V, memory @ 2133 MHz, 1.2V
15:35:24 <sech1> this is from the wall measurements
15:51:41 <hv-bridge> <xx> 6.5.1 seems worse for 1T sech1
15:56:11 <hv-bridge> <xx> tho yeah, 6.5.0 is kept there anyway
15:56:20 <hv-bridge> <xx> its really good for measuring memory tunign gains
16:03:55 <hv-bridge> <xx> then hyc will come and tell me "1T doesnt matter"
16:04:02 <hv-bridge> <xx> but its for benching man
16:04:07 <hv-bridge> <xx> rx is so useful in this
16:29:33 <hyc> lol. 1T is great if your memory is good enough
16:29:51 <hv-bridge> <xx> hyc: 1T shows memory gains so much
16:29:57 <hv-bridge> <xx> just the bench ofc
16:30:18 <hyc> a lot of DRAM won't run properly with 1T
16:30:28 <hv-bridge> <xx> no i mean 1 thread run
16:30:29 <hyc> or, not without drastically slower clocks
16:30:33 <hyc> oh
16:30:38 <hv-bridge> <xx> if you meant command rate 1T, its hard
16:30:39 <hyc> single thread?
16:30:44 <hv-bridge> <xx> i have it working on mine
16:30:45 <hv-bridge> <xx> yep
16:30:47 <hyc> yes that's what I thought you meant
16:30:58 <hv-bridge> <xx> 1T command rate is real hard
16:31:12 <hv-bridge> <xx> the 1T you see on amd is normally is like 1.5T
16:31:19 <hv-bridge> <xx> cuz geardown mode
16:31:27 <hv-bridge> <xx> very few can run that off
16:32:57 <hyc> right
16:33:12 <hv-bridge> <xx> i can stabilize that for like 3600 MHz
16:33:24 <hv-bridge> <xx> higher needs gdm on and for 4000+ i need 2T
16:34:04 <hv-bridge> <xx> https://cdn.discordapp.com/attachments/725316395428085831/775035415391633418/unknown.png
16:34:17 <hv-bridge> <xx> 3600c14 real 1T GDM off
16:34:21 <hv-bridge> <xx> https://cdn.discordapp.com/attachments/725316395428085831/775035490428256336/unknown.png
16:34:26 <hv-bridge> <xx> 4400 2T gdm off but 2T
16:34:55 <hv-bridge> <xx> 1.7V ddr4, 4333 1T gdm off
16:34:58 <hv-bridge> <xx> https://cdn.discordapp.com/attachments/725316395428085831/775035645990928434/unknown.png
16:34:59 <hv-bridge> <xx> not daily ofc
16:41:18 <hv-bridge> <xx> theres no gains in doing this though hyc
16:41:22 <hv-bridge> <xx> but good for shitposting
16:41:32 <hv-bridge> <xx> "I run ddr4 4400 for daily bruh"
16:43:07 <hyc> lol
16:43:38 <hyc> anyway, single-thread isn't relevant for a lot of reasons. mainly since processors are multicore and real workloads are multithread now
16:43:53 <hyc> but also because it's like an ideal case, no contention for shared CPU resources
16:44:13 <hyc> put more than one thread on there, contending for cache lines, and perf will drop non-linearly
16:44:59 <hv-bridge> <xx> yep
16:45:03 <hv-bridge> <xx> very nice bench though
16:45:05 <hyc> (in most cases. LMDB scales perfectly linearly across multiple cores, because all our shared data structures are cache-line aligned, to avoid contention)
16:45:15 <hv-bridge> <xx> much more sensitive than superpi or ycruncher
16:45:21 <hyc> yes
16:45:30 <hv-bridge> <xx> even shows differences in intel cache frequency
16:45:40 <hv-bridge> <xx> normal benching programs wont show it
16:45:43 <hv-bridge> <xx> rx does show it
16:45:59 <hv-bridge> <xx> hyc
16:46:00 <hv-bridge> <xx> https://cdn.discordapp.com/attachments/727089095570096211/767832498443911198/unknown.png
16:46:04 <hv-bridge> <xx> https://cdn.discordapp.com/attachments/727089095570096211/767832519830929465/unknown.png
16:46:13 <hv-bridge> <xx> just +100mhz cache
16:47:59 <hyc> nice. when you know it'll be so sensitive you can really dial in your settings
16:50:55 <sech1> \x Is it worse for single thread or just in general when running 1 thread per core?
16:51:13 <hv-bridge> <xx> single thread in general
16:51:21 <hv-bridge> <xx> see those recent 3600 submits
16:51:33 <hv-bridge> <xx> its just for --threads=1
16:51:51 <hv-bridge> <xx> https://cdn.discordapp.com/attachments/727089095570096211/775030827879890944/xmrig_6.5.1_1T_Test_2.png
16:51:55 <hv-bridge> <xx> https://cdn.discordapp.com/attachments/727089095570096211/775023309451690024/xmrig_6.5.1_1T.png
16:52:00 <hv-bridge> <xx> https://cdn.discordapp.com/attachments/727089095570096211/775023209832513536/xmrig_6.5.0_1T.png
16:52:32 <hv-bridge> <xx> wont matter for miners anyway since nT performance is better
16:52:47 <sech1> Maybe it will matter for Zen1/Zen+
16:52:52 <hv-bridge> <xx> were seeing 0.2~1% on downbins and up to 2% on perfect bins
16:52:55 <sech1> They run 1 thread per core. I need to do more testing
16:54:16 <hv-bridge> <xx> maaan i really want to see this on hwbot
16:54:20 <hv-bridge> <xx> fuck them for being slow
16:54:30 <hv-bridge> <xx> 1M 1T, 1M and 10M
16:54:36 <hv-bridge> <xx> these tiers maaan
16:55:29 <hyc> I just saw the first ryzen 5000 laptop specs, I may get onto zen3 architecture soon after all
16:55:48 <hv-bridge> <xx> isnt it lucienne that'll have double the cache
16:56:01 <hv-bridge> <xx> there will be two variants i think
16:56:03 <hyc> lucienne will be zen2, cezanne will be zen3
16:56:06 <hv-bridge> <xx> lucenne and cezanne
16:56:09 <hv-bridge> <xx> ah
16:56:38 <hv-bridge> <xx> sech1: you might see zen2 on cold this monday
16:56:52 <hv-bridge> <xx> like 8 degrees C
16:57:00 <hv-bridge> <xx> 1T is being memed so much recently
16:57:36 <hv-bridge> <xx> fullpot -190C hurts this due to fclk coldbug
18:41:47 <sech1> \x 1T performance fixed on Zen2: https://github.com/xmrig/xmrig/pull/1935
18:42:02 <sech1> even multi-thread performance got a bit better with new MSR values
18:44:15 <hv-bridge> <xx> next version then
18:45:12 <sech1> yes, 6.5.2 should be better than 6.5.0 for all configs
18:45:19 <sech1> 1T/NT/whatever
18:45:27 <sech1> or at least not worse
18:46:11 <hv-bridge> <xx> add it to release notes
18:46:52 <hv-bridge> <xx> so 6.5.0 will be 6.5.2 in 1T ?
18:54:15 <sech1> 6.5.2 = 6.5.0 in 1T on Zen2
18:54:27 <sech1> but it's even a bit faster than 6.5.1 in NT
18:54:36 <sech1> Zen3 = same as 6.5.1
19:01:11 <hv-bridge> <coffee> ok
19:20:41 <hv-bridge> <coffee> people are addicted in dogpiling one thread runs
19:20:52 <hv-bridge> <coffee> thank for this benchmark, hope it get in hwbot
19:24:38 <sech1> if 100 people write to info⊙ho maybe it will help get it there faster
19:26:25 <sech1> I guess the fact that fastest Ryzens run just below 1000 seconds makes people even more addicted. Everyone wants to get sub 1000 :D
19:33:58 <hv-bridge> <xx> have you posted on r/moneromining about this?
19:34:07 <hv-bridge> <xx> challenge them
19:35:25 <hv-bridge> <xx> sech1 ^
19:35:41 <hv-bridge> <xx> i think its ready for primetime now as im already seeing 12-11-11 runs
19:37:21 <sech1> miners are not benchers
19:37:32 <sech1> they're interested in 24/7 stable settings
19:46:17 <hv-bridge> <coffee> i say better post in r/overclocking
19:46:31 <hv-bridge> <coffee> can entice them say this respond well to system tuning
19:50:27 <sech1> RandomX doesn't write to memory at all, so write-related timings don't make a difference
19:51:33 <hv-bridge> <coffee> threadripper does not work well in 6.5.1
19:51:39 <hv-bridge> <coffee> have just submitted
19:52:26 <hv-bridge> <xx> gnasherr's sub
19:54:08 <hv-bridge> <coffee> will be a what the fuck moment
19:54:10 <hv-bridge> <coffee> https://cdn.discordapp.com/attachments/328891236918493184/775085640286339072/IMG_MJL_-No-XML-_20201108_195306065.jpg
20:12:08 <hv-bridge> <coffee> https://cdn.discordapp.com/attachments/328891236918493184/775090224836902922/unknown.png
20:12:14 <hv-bridge> <coffee> 😉
23:45:26 <hv-bridge> <coffee> https://cdn.discordapp.com/attachments/305983092902985728/775104405908226078/1t_big_dicc.png
23:45:28 <hv-bridge> <coffee> hi
23:45:56 <hv-bridge> <coffee> sech1 can check