News for hackers. Stuff that matters.
Re:The ABCs of virtual private servers, Part 1: Why go virtual? by sparky on Thursday February 17, 2011 @04:35AM (#2230390)
Memory capacity is typically dedicated (e.g., Linode), but memory bandwidth is difficult to allocate statically, and can be a huge problem even if you're fine on capacity. For example, a simulator I like to run has a 50-60MB working set, much larger than on-chip cache but well under my allocated 512MB of RAM. However, other concurrent users can disproportionately use up DRAM bandwidth, depending on their access pattern and the OS scheduler.
Re:The ABCs of virtual private servers, Part 1: Why go virtual? by tres on Thursday February 17, 2011 @05:46AM (#2230511)
I've never seen a hardware node get anywhere near saturating the bus before disk I/O became an issue. So yes, there is a potential for saturation; however, I'd be really happy if that were my capacity bottleneck.
Re:The ABCs of virtual private servers, Part 1: Why go virtual? by gaius on Thursday February 17, 2011 @07:10AM (#2230641)
Again this is a platform specific complaint, back in the day IRIX solved this with GRIO on their Xbow active backplane. This technology will make it into Linux PCs eventually I expect.