... and Windows 9 was never called Windows IXWindows 10 never ever was called X…
... and Windows 9 was never called Windows IXWindows 10 never ever was called X…
never said it was called X, i call it X & wrote is as such...Windows 10 never ever was called X…
cDMP (Cheese Grater Dual Mac Pro)Windows 10 never ever was called X. What is a cDMP?
If you want to write cMP, people will understood but it's not correct, it's a MP4,1 or a MP5,1. If you want to specify a 2009 with MP5,1 firmware, write 4,1>5,1. Use the correct acronyms.
This exists only in your mind.never said it was called X, i call it X & wrote is as such...
[doublepost=1552255515][/doublepost]
cDMP (Cheese Grater Dual Mac Pro)
& yet my mind DOES indeed exist......This exists only in your mind.
If you used the correct terms, no one would misinterpreted or replied alerting you…
[doublepost=1552255665][/doublepost]
& yet my mind DOES indeed exist......
How is all this related the topic about the ram exactly?
It's very simple - if you want to discuss something on the forum, it's better to use the common nomenclature than to speak in a code that only you understand.How is all this related the topic about the ram exactly?
about time - someone with a reasonable question/requestWindows 10 Pro 64 bit supports up to 512 GB. Can you test 6x32 GB and 8x32 GB?
Understood, but i've always called Windows 10 - Windows X (just as an FYI for my defence)It's very simple - if you want to discuss something on the forum, it's better to use the common nomenclature than to speak in a code that only you understand.
There are lots of typos (and English as a second, third, or fourth language) here - so it's quite reasonable to interpret "Windows X" as a typo for "Windows XP", not as a neologism for "Windows 10".
sounds like you've got a grudge, i don't have one ;-)If you used the correct terms, no one would misinterpreted or replied alerting you…
i've updated/edited my posts with correct acronymsWindows 10 never ever was called X. What is a cDMP?
If you want to write cMP, people will understood but it's not correct, it's a MP4,1 or a MP5,1. If you want to specify a 2009 with MP5,1 firmware, write 4,1>5,1. Use the correct acronyms.
so far not the best...Any news?
not too sure if thats meant for me but i am in NO WAY mixing OWC's memory modulesHere is a warning from OWC even though it is for their modules bare in mind mixing different module types might not work.
"OWC p/n OWC1333D3MPE8GB (8GB modules) and OWC1333D3MPE16G (16GB modules) require that all installed modules be of the same p/n OWC 8GB and/or 16GB modules. Other existing Apple or 3rd party 1GB, 2GB and 4GB modules are not supported for use with these kits and need to be removed when these modules are added."
It is strange that Windows does not recognize all modules though
Cheers mate - thanks for the heads up (Yes i am running 2 x 2.26GHz Xeon's) which are in the Mid 2009 Mac Pro 4,1 --> 5,1 firmware updateYou can easily test each modules one by one and just follow this red LED. If it's showing even with one module then it's faulty - just run memtest on it and it should show errors right away.
Otherwise we are hitting a wall here. I think your CPU might be a limit - E5520 should support no more than 144 GB: https://ark.intel.com/content/www/u...20-8m-cache-2-26-ghz-5-86-gt-s-intel-qpi.html
X5690 can handle up to 288 GB so it should work. It would be awesome to see a 192 GB working setup as it should offer the best performance.
Geekbench should show big difference between 192 GB (triple channel) and 256 GB (dual channel).
quite right, but its still way much more memory than the 6 x 16GB (96GB)Flex mode is NOT dual channel.
The slot 3 and 4 (also 7 and 8) has its OWN channel. It's impossible to run all 8 DIMM with just dual channel on cMP.
So far i've got 4 x 32GB + 2 x 16GB (160GB Total) to work OK with the 2 x 2.26GHz 4,1 --> 5,1Same for me. Would be nice to see 6x16 GB vs 6x32 GB tests in Geekbench.
ramdisk is not faster than nVME ssd. Even in raid. But surely if you have a lot of unused RAM then you can put it to useful work.fantastic news!
more than real speed gain for system itself it alows to do larger ramdisk for cache in adobe software !!!
well i gess some PC broker are going to wonder why they sale so much 32gb ram modules sudenly!!!!
Geekbench memory speed tests often don't reflect real application performance. (Geekbench effectively disables the caches for the memory tests, real applications exploit the caches.)Geekbench should show big difference between 192 GB (triple channel) and 256 GB (dual channel).
https://forums.macrumors.com/thread...th-various-mem-configs.1704700/#post-18745317
Looking at the group scores:Code:1 DIMM 2 DIMM 3 DIMM 4 DIMM ------- ------- ------- ------- Floating Point Single 3825 3826 3828 3836 Floating Point Multi 25531 25555 25529 25522 Integer Single 3625 3641 3655 3646 Integer Multi 20959 22686 23768 24282
So,
- virtual 4-way tie on Floating Single
- virtual 4-way tie on Floating Multi-core
- virtual 4-way tie on Integer Single
- 1 DIMM is 86% of 4 DIMMs on Integer multi - but if you removed AES and Dijkstra you'd have a virtual 4-way tie, the rest of the integer multi tests were virtual ties
Those L3 caches do seem to be effective on "non-bandwidth virus" programs.