Met Office to build £97m supercomputer
bbc.co.uk
bbc.co.uk
[1] http://investors.cray.com/phoenix.zhtml?c=98390&p=irol-newsA...
- quantitative information about the new system's power relative to its predecessor ("13 times more powerful"; I assume they mean something like "13x faster on typical workloads")
- quantitative information about its speed in absolute terms ("more than 16,000 trillion calculations per second")
- quantitative information about what it will let them do that they couldn't before ("forecast updates every hour", "very high resolution (300m) models", and few particular projects they intend to use it for)
- a little more tech-spec information, albeit stupidly presented ("120,000 times more memory than a top-end smartphone", which I presume means either 120TB or 240TB)
- how much they're spending
- how long they expect it to take to get it set up and working
and they do give the weight in tonnes as well as in double-decker buses. I don't really see that there's much of a problem here.
Maybe I'm missing something but should a 13x speedup allow it to run in 1/13th the time? Or maybe the "13x" is only for part of the system and they have a bottleneck somewhere else.
Edit: A quote later in the article says "It will allow us to add more precision, more detail, more accuracy". So it's probably increasing the resolution even though the part you quoted sounds like it's not.
And this is weather simulation so stuff like network topology matters and they will be running their models as often as they can.
The cloud wins for more elastic work loads and people without IT departments and server rooms.
Let's say an order of magnitude speed improvement. :wow:
I wonder if it will be able to model the local microclimate effect of powering and cooling 140 tonnes of compute?
Given its a constant operation which probably requires high speed interconnects. However it would be interesting to see how close in cost cloud is to a bare metal build.
We run a small clustered database across 8 nodes. Total cost for the hardware was ~ $3000 per node. Cost for a comparable node in EC2 per month? $1500. Even with co-lo costs for power and bandwidth, and buying 10gige switches it's far cheaper for us to host it in house than it is to use EC2.
That doesn't mean it's not useful, but it's still tens of times more expensive than using your own hardware.
Also, things are changing, but it is/was hard to ear mark funds for the cloud in a grant so spending the money up front was often what needed to happen.
While some cloud providers now have very high-speed, low-latency interconnects, they only scale so wide in a virtual environment. This is due to limitations in the physical datacenter space and the way node provisioning works on the back-end. If you truly need extremely wide, low-latency, high bandwidth interconnect for a large period of time, on-prem is still (probably) your best option.
http://en.wikipedia.org/wiki/Numerical_weather_prediction#Co...