grin network 51% attack ongoing

so much for asic-friendly safety

weren't they shifting to asics?

They should be at asic-only algorithm after almost 2 years since launch

aren't they using cuckoo cycle?

yes, but they have asic version which doesn't change and non-asic version which changes twice a year

Zen2 vs Zen3 at different scratchpad sizes: paste.debian.net/1170471

Zen3 is 4.43% faster with 256 KB scratchpad where L3 doesn't matter

and almost 5% slower on cn-heavy with its 4 MB scratchpad

So it's +4.4% IPC on RandomX, but slow L3 cache negates it

why does the rest of cryptoworld think asics are fine and to be embraced?

in trying to find out what the current state of grin PoW is, i've stumbled on this: forum.grin.mw/t/grin-improvement-pr…ephrase-primary-pow-commitment/4653

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." >>> tronweekly.com/mimblewimble-grin-suffe

ck/

but thats from the cryptonews sources which are rarely accurate

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.

3750 MHz @ 0.85V, memory @ 2133 MHz, 1.2V

this is from the wall measurements

<xx> 6.5.1 seems worse for 1T sech1

<xx> tho yeah, 6.5.0 is kept there anyway

<xx> its really good for measuring memory tunign gains

<xx> then hyc will come and tell me "1T doesnt matter"

<xx> but its for benching man

<xx> rx is so useful in this

lol. 1T is great if your memory is good enough

<xx> hyc: 1T shows memory gains so much

<xx> just the bench ofc

a lot of DRAM won't run properly with 1T

<xx> no i mean 1 thread run

or, not without drastically slower clocks

oh

<xx> if you meant command rate 1T, its hard

single thread?

<xx> i have it working on mine

<xx> yep

yes that's what I thought you meant

<xx> 1T command rate is real hard

<xx> the 1T you see on amd is normally is like 1.5T

<xx> cuz geardown mode

<xx> very few can run that off

right

<xx> i can stabilize that for like 3600 MHz

<xx> higher needs gdm on and for 4000+ i need 2T

<xx> cdn.discordapp.com/attachments/7253…5831/775035415391633418/unknown.png

<xx> 3600c14 real 1T GDM off

<xx> cdn.discordapp.com/attachments/7253…5831/775035490428256336/unknown.png

<xx> 4400 2T gdm off but 2T

<xx> 1.7V ddr4, 4333 1T gdm off

<xx> cdn.discordapp.com/attachments/7253…5831/775035645990928434/unknown.png

<xx> not daily ofc

<xx> theres no gains in doing this though hyc

<xx> but good for shitposting

<xx> "I run ddr4 4400 for daily bruh"

lol

anyway, single-thread isn't relevant for a lot of reasons. mainly since processors are multicore and real workloads are multithread now

but also because it's like an ideal case, no contention for shared CPU resources

put more than one thread on there, contending for cache lines, and perf will drop non-linearly

<xx> yep

<xx> very nice bench though

(in most cases. LMDB scales perfectly linearly across multiple cores, because all our shared data structures are cache-line aligned, to avoid contention)

<xx> much more sensitive than superpi or ycruncher

yes

<xx> even shows differences in intel cache frequency

<xx> normal benching programs wont show it

<xx> rx does show it

<xx> hyc

<xx> cdn.discordapp.com/attachments/7270…6211/767832498443911198/unknown.png

<xx> cdn.discordapp.com/attachments/7270…6211/767832519830929465/unknown.png

<xx> just +100mhz cache

nice. when you know it'll be so sensitive you can really dial in your settings

\x Is it worse for single thread or just in general when running 1 thread per core?

<xx> single thread in general

<xx> see those recent 3600 submits

<xx> its just for --threads=1

<xx> cdn.discordapp.com/attachments/7270…879890944/xmrig_6.5.1_1T_Test_2.png

<xx> cdn.discordapp.com/attachments/7270…5023309451690024/xmrig_6.5.1_1T.png

<xx> cdn.discordapp.com/attachments/7270…5023209832513536/xmrig_6.5.0_1T.png

<xx> wont matter for miners anyway since nT performance is better

Maybe it will matter for Zen1/Zen+

<xx> were seeing 0.2~1% on downbins and up to 2% on perfect bins

They run 1 thread per core. I need to do more testing

<xx> maaan i really want to see this on hwbot

<xx> fuck them for being slow

<xx> 1M 1T, 1M and 10M

<xx> these tiers maaan

I just saw the first ryzen 5000 laptop specs, I may get onto zen3 architecture soon after all

<xx> isnt it lucienne that'll have double the cache

<xx> there will be two variants i think

lucienne will be zen2, cezanne will be zen3

<xx> lucenne and cezanne

<xx> ah

<xx> sech1: you might see zen2 on cold this monday

<xx> like 8 degrees C

<xx> 1T is being memed so much recently

<xx> fullpot -190C hurts this due to fclk coldbug

\x 1T performance fixed on Zen2: xmrig/xmrig #1935

even multi-thread performance got a bit better with new MSR values

<xx> next version then

yes, 6.5.2 should be better than 6.5.0 for all configs

1T/NT/whatever

or at least not worse

<xx> add it to release notes

<xx> so 6.5.0 will be 6.5.2 in 1T ?

6.5.2 = 6.5.0 in 1T on Zen2

but it's even a bit faster than 6.5.1 in NT

Zen3 = same as 6.5.1

<coffee> ok

<coffee> people are addicted in dogpiling one thread runs

<coffee> thank for this benchmark, hope it get in hwbot

if 100 people write to info⊙ho maybe it will help get it there faster

I guess the fact that fastest Ryzens run just below 1000 seconds makes people even more addicted. Everyone wants to get sub 1000 :D

<xx> have you posted on r/moneromining about this?

<xx> challenge them

<xx> sech1 ^

<xx> i think its ready for primetime now as im already seeing 12-11-11 runs

miners are not benchers

they're interested in 24/7 stable settings

<coffee> i say better post in r/overclocking

<coffee> can entice them say this respond well to system tuning

RandomX doesn't write to memory at all, so write-related timings don't make a difference

<coffee> threadripper does not work well in 6.5.1

<coffee> have just submitted

<xx> gnasherr's sub

<coffee> will be a what the fuck moment

<coffee> cdn.discordapp.com/attachments/3288…MJL_-No-XML-_20201108_195306065.jpg

<coffee> cdn.discordapp.com/attachments/3288…3184/775090224836902922/unknown.png

<coffee> 😉

<coffee> cdn.discordapp.com/attachments/3059…/775104405908226078/1t_big_dicc.png

<coffee> hi

<coffee> sech1 can check