Shoehorning a CPU with 8 memory channels into an existing socket/motherboard infrastructure designed for a CPU with four channels seems like a bit of a challenge!
22 publicly visible posts • joined 6 Jun 2008
The other possibility is that this is about doing something for energy efficient servers in large cloud data centers. I agree with others, don't think ARM is a good fit for XBox unless they plan to do most of the hard work in the GPU and see the processor as more of a conductor than an orchestra.
"Joining the 750s will be as-yet-unnumbered 3.2GHz, 3.33GHz and 3.46GHz i5s which contain only two cores, though HyperThreading technology - absent from the first i5 - will present eight cores to the host OS. All three will contain 4MB of L3 cache."
Unless Intel is doing 4 hyperthreads/core, I think that's going to be four cores (or threads) not eight.
The fire control and targetting stuff for a laser is much simpler and probably faster because:
1. The laser beam doesn't drop with distance, so no need to correct for that, which makes getting on target in the vertical axis is simpler
2. It arrives at the target almost instantaneously (i.e. the speed of light vs. a few thousand feet/sec), so the need to account for the target's movement is much reduced, which means that getting on target in the horizontal axis is simpler
All in all, I would suspect that Gatling guns would be rapidly displaced in most applications if this stuff actually works.
If 384 GB was really needed for virtualization on a two processor system, you have to ask why Cisco didn't use the VMmark benchmark results they published to prove the point. But funnily enough they used the same amount of memory as just about everybody else (96 GB in the form of 12x8GB DIMMs). To me this suggests that memory beyond 96GB for a dual processor is probably a waste unless you have workloads that have a very large memory footprint relative to CPU and I/O requirements.
The Dynamic Cube BX900 blade server as announced will never support Nehalem EX, you can't drop Nehalem EX processors into any existing XEON design, it requires a whole new motherboard. It seems unlikely that they would have announced a conventional XEON blade if they expected Nehalem EX to be pulled in by six months as it would be obsolete by time it started to ship. So my guess is that availability date for Nehalem EX is unchanged and that systems will show up in late-Q4 to early Q1.
I'm part of the W7 private beta (and for every previous beta back to NT 3.1), and I'm very happy so far, does that cancel out chris123. Seemed to me that his post was partly sour grapes that we hadn't received any intermediate builds, he didn't have any specific problems with W7 beta 1 that I could see.
First, the usual unfounded Observation that an Apple server OS would be more secure than W2K08. Care to justify that a little Tim, it's pretty sweeping statement given that there have been no major security issues with W2K08.
Then there's the whole issue of building an enterprise hardware and software support organization to go along with the servers. Just having the boxes isn't enough, you need a full enterprise support organization or folks will just laugh at you.
This might be a more intersting article if it happened to mention what variety of Windows it refers to. For example, if "unpatched Windows" refers to say Windows XP SP1, then this revelation comes in the "duh, no s**t Sherlock" category. If however it refers to say Windows Vista without SP1 installed, then its a tad more alarmainf
Yes, they do, but they are still limited by the number of physical I/Os that the hard disk can handle. Lets say there is an 80% cache hit rate, that means 20% of I/Os have to be satisfied from the hard disks. Now assume 20 drives each capable of 300 IOPs, that 20% can't exceed 6000 IOPs, so overall throughput in real world applications is going to peak at around 30K IOPs, regardless of hw fast the cache is.
If you replace those twenty drives with 10 SSDs each capable of 1000 IOPs and you've got 10,000 IOPs from disk, or 50,000 IOPs overall.
SSD is inevitable, and will ultimately kill what we think of as high performance drives (i.e. 15K RPM FC drives)