32-bit vms also "generally" perform better on XenServer (depending on the workload). The issue with 32-bit Linux is that it has usually only has 800M for so for available for the kernel [1]. This limits the number of connections that can be tracked by the conntrack module to around 800/300 =~ 2.5 million. Of course this leave little space for other kernel tasks.
If you've got a busy web site behind CloudStack's HAProxy then this may not be enough. [1] http://unix.stackexchange.com/questions/4929/what-are-high-memory-and-low-m emory-on-linux On 10/23/13 10:21 AM, "Marty Sweet" <msweet....@gmail.com> wrote: >What would be the main reasoning behind this change? Surely the >minimalistic specifications that SystemVMs are assigned suit 32-bit better >in terms of Memory? > >"The main disadvantage of 64-bit architectures is that, relative to 32-bit >architectures, the same data occupies more space in memory (due to longer >pointers and possibly other types, and alignment padding). This increases >the memory requirements of a given process and can have implications for >efficient processor cache utilization." > > >On Wed, Oct 23, 2013 at 1:48 PM, Abhinandan Prateek < >abhinandan.prat...@citrix.com> wrote: > >> On 23/10/13 3:48 pm, "David Nalley" <da...@gnsa.us> wrote: >> >> >On Wed, Oct 23, 2013 at 1:32 AM, Abhinandan Prateek >> ><abhinandan.prat...@citrix.com> wrote: >> >> >> >> We are planning to make 64-bit system vm templates as default >> >>offering in 4.2.1. >> >> This is an initial email to have thoughts from the community on this. >> >> >> >> -abhi >> > >> >-1 >> >Who is this we? >> >I agree with Wido We adhere to semver, and accordingly 4.2.1 should be >> >a bugfix release. >> >> We were some of the fellow committers, even I was of the same thinking >>but >> thought it will be good to have a general opinion. >> >> -abhi >> >>
