The same holds true. 8 GB per channel. If you put both channels in, you still only get 8GB max usable.
That board allows you to put in a single 8GB DIMM and use all of it.
NOTICE I did not say installable. I said usable.
The same holds true. 8 GB per channel. If you put both channels in, you still only get 8GB max usable.
That board allows you to put in a single 8GB DIMM and use all of it.
NOTICE I did not say installable. I said usable.
Where is your prof of “usable”?
According to your theory there should be no difference
Synology DiskStation DS218+ (10GB) vs Synology DiskStation DS218+ (16GB)
https://browser.geekbench.com/v4/cpu/compare/4595839?baseline=4725933
Break out the C compiler.
Write a for loop which performs kmem_alloc, printing out each Gigabyte as it’s successfully allocated.
Allocating in user space simply goes to the swap partition and is therefore meaningless.
Kernel memory is not swappable.
I would create a 10Gb random file, get the hash, move it to /tmp mounted in memory and hash it again. Willing to bet it would not match (provided the system would not crash). I would rather trust Intel than asrock…
Something like if=/dev/urandom of=target-file bs=1M count=10000
Phil
I have made some phone calls and between several of us (joint call), we think we have this reasonably resolved.
Some of you will be pleased, some not, as there is no definitive answer.
Here is our conclusion (we are all EE’s or CE’s. Please understand this is our best effort ) so this matter may be resolved once and for all.
We therefore conclude, in the 3 years since this started,
Further,
In summary,
Where does this leave Synology users?
Only Synology knows when they purchased the chips they have on hand.
Are they early production or later production. What was the tray price because tray price is indicative of bins they came from (positions on the die)
I have a DS718+ with 16 GB Ram, of that I have allocated 14 GB to a Windows VM and have had software in Windows 10 VM report that it is using greater than 8 GB.
I am going to close this thread so we don’t have a long run-on list of confirmations which serves no real purpose.
What is known and unknown has been stated; there are many alternative sources making their statements.
From Plex’s perspective, This is a hardware issue outside of the scope of running PMS.