AMD Ryzen 7 5800X3D Continues Showing Much Potential For 3D V-Cache In Technical Computing

[atomsymbol]

Something is off with the xmrig benchmarks. Neither of them are near where they should be, at least for the Monero variant, and other benchmarks have shown that the 5800X3D variant is roughly on-par with the 5800X if not a tad slower (not counting overclocking). This is because the RandomX algorithm already uses 2MB/thread which the 5800X can handle fine.

Basically, don't get the 5800X3D expecting faster monero mining performance. I've been able to personally confirm this .

If by "2MB/thread" you don't mean pagesize: With 5800X3D it could use 6MB/thread (6MB*16=96MB), no?

One of the xmrig developers has to get her/his hands on an 5800X3D before it can be concluded whether 5800X3D has a hashrate similar to 5800X.

[fuzz]

If by "2MB/thread" you don't mean pagesize: With 5800X3D it could use 6MB/thread (6MB*16=96MB), no?

One of the xmrig developers has to get her/his hands on an 5800X3D before it can be concluded whether 5800X3D has a hashrate similar to 5800X.

It's a strict limitation of the RandomX algorithm, necessary because of the nature of distributed proof of work. I think anything else would be a new algorithm and not necessarily usable by Monero.

[atomsymbol]

It's a strict limitation of the RandomX algorithm, necessary because of the nature of distributed proof of work. I think anything else would be a new algorithm and not necessarily usable by Monero.

Are you sure that executing 2 or 3 RandomX programs per 1 CPU thread (because 5800X3D has enough L3 cache to run multiple RandomX programs per core) will fail to achieve a significantly higher (such as: +25%) hashrate?

[fuzz]

Are you sure that executing 2 or 3 RandomX programs per 1 CPU thread (because 5800X3D has enough L3 cache to run multiple RandomX programs per core) will fail to achieve a significantly higher (such as: +25%) hashrate?

Indeed, that is one of the first things the xmrig developers suggested to me. It only reduced the hash rate (though not too much).

[atomsymbol]

Indeed, that is one of the first things the xmrig developers suggested to me. It only reduced the hash rate (though not too much).

I suspect that the problem is that by "executing 2 or 3 RandomX programs per 1 CPU thread" I meant something totally different from what you believe I meant. I didn't mean simply running "xmrig --threads=32" on the 8-core 16-thread 5800X3D. I meant the following: fine-grained software interleaving of 2 or 3 RandomX programs with the goal of trying to increase IPC (instructions per clock) on Ryzen 5800X3D. It is non-trivial to implement such interleaving.

I am sorry about the confusion.