because DDR3 only goes up to 8GB, requiring registered modules to go beyond that, which in turn requires server motherboards/CPUs to utilize (and gets very expensive)
At the time there were no 8Gb SDRAM chips to test with. Column and Row are multiplexed on the same data lines and while there are reserved column addresses for special function there are enough for higher densities.Note: DIMM module support is based on availability and is subject to change.
The JEDEC specifications for DDR3 do account for the use of 8 Gbit packages (either one 8 Gbit die or two 4 Gbit dies per package), should these be available. However I am told that currently there is a fundamental non-fixable issue on all Intel processors (except Avoton and Rangeley, other Silvermont (BayTrail) is affected) that means that these dies are not recognised. In their specifications for Ivy Bridge-E, Intel do state that 8Gb packages are supported (link, page 10), however this apparently has not been the case so far and I'M is working with motherboard manufacturers to further pin down this issue.
No, it's about virtualization. There's no way I'm sharing OS with the kids for my next computer. That combined with an ITX build just being a whole lot less of an eye sore makes 16GB dimms very attractive for me.
I'm new to the whole virtualization scene. How will that work? Do you leave the native OS install to kids for games and what not and simply run a VM for yourself? Or is there a specially VM OS you install that you use to virtualize all OSs?
Does virtualization sap performance?
basically...
u have a Vsphere... that is the main OS which your computer boots up.
Then inside the Vsphere, your system sets up Virtualized OS's.
So you basically install an OS ontop of that OS.
You can repeat as many OS's installs u require.
Does it Tap resources?
Yes it does.
You can set and assign cores / ram / HDD space specific to the OS installed, on the Sphere.
The more Virtualized client you need, the more resources you will need. Ie. cores, Ram and storage spaces.
A lot of people i know use eSXi, as its very small and lite.
Others use windows Server 2012 with Hyper-V, but this route requires a LOT of resources.