ClioSport.net
Register a free account today to become a member!
Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
-
When you purchase through links on our site, we may earn an affiliate commission. Read more here.
Server blades
- Thread starter BenWall
- Start date
Re: Sever blades
it has nothing to do with it been on blades its all down to the cpu on the most basic level and it gets artificially limited by the os
32bit cpu supports 4gig ram
64bit supports 16 exabytes of ram
windows 2003 enterprise 64bit (and above) supports 1TB
an explanation
A 32-bit register meant that 232 addresses, or 4 gigabytes of RAM, could be referenced. At the time these architectures were devised, 4 gigabytes of memory was so far beyond the typical quantities available in installations that this was considered to be enough "headroom" for addressing. 4-gigabyte addresses were considered an appropriate size to work with for another important reason: 4 billion integers are enough to assign unique references to most physically countable things in applications like databases.
The emergence of the 64-bit architecture effectively increases the memory ceiling to 264 addresses, equivalent to 17,179,869,184 gigabytes or 16 exabytes of RAM. To put this in perspective, in the days when a mere 4 MB of main memory was commonplace, the maximum memory ceiling of 232 addresses was about 1000 times larger than typical memory configurations. Taking today's standard as 4 GB of main memory (actually, few personal computers have this much), then the difference between today's standard and the 264 limit is a factor of about 4 billion. Most 64-bit consumer PCs on the market today have an artificial limit on the amount of memory they can recognize, because physical constraints make it highly unlikely that one will need support for the full 16 exabyte capacity. Apple's Mac Pro, for example, can be physically configured with up to 16 gigabytes of memory, and as such there is no need for support beyond that amount. A recent linux kernel (version 2.6.16) can be compiled with support for up to 64 gigabytes of memory
it has nothing to do with it been on blades its all down to the cpu on the most basic level and it gets artificially limited by the os
32bit cpu supports 4gig ram
64bit supports 16 exabytes of ram
windows 2003 enterprise 64bit (and above) supports 1TB
an explanation
A 32-bit register meant that 232 addresses, or 4 gigabytes of RAM, could be referenced. At the time these architectures were devised, 4 gigabytes of memory was so far beyond the typical quantities available in installations that this was considered to be enough "headroom" for addressing. 4-gigabyte addresses were considered an appropriate size to work with for another important reason: 4 billion integers are enough to assign unique references to most physically countable things in applications like databases.
The emergence of the 64-bit architecture effectively increases the memory ceiling to 264 addresses, equivalent to 17,179,869,184 gigabytes or 16 exabytes of RAM. To put this in perspective, in the days when a mere 4 MB of main memory was commonplace, the maximum memory ceiling of 232 addresses was about 1000 times larger than typical memory configurations. Taking today's standard as 4 GB of main memory (actually, few personal computers have this much), then the difference between today's standard and the 264 limit is a factor of about 4 billion. Most 64-bit consumer PCs on the market today have an artificial limit on the amount of memory they can recognize, because physical constraints make it highly unlikely that one will need support for the full 16 exabyte capacity. Apple's Mac Pro, for example, can be physically configured with up to 16 gigabytes of memory, and as such there is no need for support beyond that amount. A recent linux kernel (version 2.6.16) can be compiled with support for up to 64 gigabytes of memory
Re: Sever blades
windows server 2003 standard only supports 4gb ram though whether on a 32 bit or 64 bit machine (license not physical capability)
Blade servers still require their own OS, if you want that amount of memory or processing power you would be looking at Integrity servers (Superdome) which use the Itanium 2 DC processor and can support 62 (128 cores) and 1TB ram, but you would need one hell of an application to need that sort of spec, mostly that would be split down into N-pars and runnig several servers.
There is an integrity Blade from HP but its very limited in spec due to the size contraints of the blade enclosure, so its only really designed as a small tru 64bit server but not to the scale of the rack integrity servers.
I guess you could create a blade server farm but even then each blade server only has 8 slots using 4gb dimms means 1/2 TB in one c-class enclosure.
windows server 2003 standard only supports 4gb ram though whether on a 32 bit or 64 bit machine (license not physical capability)
Blade servers still require their own OS, if you want that amount of memory or processing power you would be looking at Integrity servers (Superdome) which use the Itanium 2 DC processor and can support 62 (128 cores) and 1TB ram, but you would need one hell of an application to need that sort of spec, mostly that would be split down into N-pars and runnig several servers.
There is an integrity Blade from HP but its very limited in spec due to the size contraints of the blade enclosure, so its only really designed as a small tru 64bit server but not to the scale of the rack integrity servers.
I guess you could create a blade server farm but even then each blade server only has 8 slots using 4gb dimms means 1/2 TB in one c-class enclosure.
