-
gingeropolous
aw hes gone
-
gingeropolous
ive always thought a pool could offer exclusive baller remote node service for their miners
-
gingeropolous
like, theoretically the daemons on a dope box to begin with
-
gingeropolous
all the up down bandwidth 10 gps
-
sech1
-
hyc
cute
-
hyc
but if you're running any other processes concurrent with mining, you've already made it clear that mining isn't your #1 priority
-
fort3hlulz
Its a great feature for normal people using their existing comps to mine
-
fort3hlulz
Which is a unique thing enabled in Monero
-
hyc
seems gratuitous to me. blocking other processes from accessing L3 cache means they all run slower
-
hyc
if you're actually doing work on your computer, and just run a few mining threads as background activity, this is not the kind of prioritization you want
-
fort3hlulz
But it means you can mine at a higher hashrate while still having usability of the PC (albeit with slightly worse performance)
-
fort3hlulz
Its a good option to have IMO
-
hyc
if you want mining to be your #1 priority. just don't run anything else
-
fort3hlulz
well obviously yeah
-
sech1
hyc the theory is that new Ryzen 4000 APUs will have more cores than they can allocate to RandomX. In theory, it should be possible to run them at near max hashrate AND do something productive on the remaining cores at the same time
-
hyc
no different than Intel that is already too cache-starved to use all cores
-
hyc
but the point remains, denying other cores the use of L3 means everything else you do will be much slower
-
hyc
so if you're trying to do productive owrk on your PC, and a little mining on the side, this is a stupid option
-
moneromooo
Depending on the type of other work, some slowness is typically left unnoticed. Like mostly when typing, and causing occasional incremental processing.
-
moneromooo
Sure, if you're considering number crunching, building, etc, but many people don't do that most of the time.
-
moneromooo
Guess it prevents pointless cache dirtying.
-
sech1
hyc well, Zen2 has 512 KB L2 cache per core, so it won't be that bad even without L3. And I wasn't talking about number crunching. In my case it's mostly typing and occasional code compilation and some browsing 99% of the time.
-
gethh
the feature would be if miner scale it self down when usage is detected leaving some L3 for regular tasks
-
gethh