>> again, if you have a bursty load, you want to use a shared facility,
>> of which, EC2 spot instances is just one example.
>
> When talking of using a shared facility: The advantage I've
> sometimes seen for "cloud" over the traditional "get time on a
> shared cluster"
I should be clear - the ki
http://hometown-pasadena.com/history/a-very-punny-mystery-resolved/8428
Reddi-Whip is VERY different from Cool-Whip.. the former is basically whipping
cream (with sugar and carageneen) in a can pressurized with nitrous oxide
(which has good properties for whipping cream). Consumption of the pro
I think the change in scale over the past 10-15 years is interesting, and
especially the changes in architecture that result from this.
Going from 8-16 processors to 1000s is a big change. Bisection bandwidth on
your comm fabric. How do you boot.. 8 processors can be booted sequentially or
si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> again, if you have a bursty load, you want to use a shared facility,
> of which, EC2 spot instances is just one example.
When talking of using a shared facility: The advantage I've
sometimes seen for "cloud" over the traditional "get time on a
s
Jorg,
Thanks for the the additional details. You addressed all of my concerns.
I wish the original article had these details. Unfortunately, I think
the original article simplified things a bit to much, and was a bit
optimistic about running one of these in a dessert.
Oh come on. We've had so
Am 04.03.2013 um 12:38 schrieb Hearns, John:
>> Utility being a phrase that identifies how one can
>> turn on and off resource at the drop of a hat. If you are running
>> nodes 100% 365d/y on prem is still a serious win. If you have the odd
>> monster run, or are in a small shop with no access t
>> http://www.hpcwire.com/hpcwire/2013-02-28/utility_supercomputing_heats_up.html
>
> well, it's HPC wire - I always assume their name is acknowledgement that
> their content is much like "HPC PR wire", often or mostly
> vendor-sponsored.
> call me ivory-tower, but this sort of thing:
>
> Cy
On 03/04/2013 09:26 AM, Hearns, John wrote:
> Jorg,
>
> Thanks for the the additional details. You addressed all of my concerns.
> I wish the original article had these details. Unfortunately, I think
> the original article simplified things a bit to much, and was a bit
> optimistic about running o
Jorg,
Thanks for the the additional details. You addressed all of my concerns.
I wish the original article had these details. Unfortunately, I think
the original article simplified things a bit to much, and was a bit
optimistic about running one of these in a dessert.
--
Prentice
On 03/01/201
On Sun, Mar 3, 2013 at 12:31 PM, Mark Hahn wrote:
>>>
>>> I'm guessing the answer is that your market is mainly people who are too
>>> self-important (anything health- or finance-related) to do it themselves
>>> (or join a coop/consortium), or else people just getting their toes wet.
>
>
> James,
>> Utility being a phrase that identifies how one can
>> turn on and off resource at the drop of a hat. If you are running
>> nodes 100% 365d/y on prem is still a serious win. If you have the odd
>> monster run, or are in a small shop with no access to large scale
>> compute, utility is the only
> Utility being a phrase that identifies how one can
> turn on and off resource at the drop of a hat. If you are running
> nodes 100% 365d/y on prem is still a serious win. If you have the odd
> monster run, or are in a small shop with no access to large scale
> compute, utility is the only way
Given that this a talk to a LUG, how about:
Introducing what a supercomputer is
Take a look at the top500 list - and point out that around 90% of the systems
there run Linux
Maybe as a theme for your talk take the Linux kernel - it runs on everything
from an embedded device, though an Android
13 matches
Mail list logo
