<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
This was a cloud-based solution id3as built for Thomson Reuters that
completely virtualised their online communications business that
they run for most FTSE / NYSE companies. Our experience was that
Erlang played nicely when in a star topology and (understandably)
got very upset at these levels of scale when in a fully connected
environment. We create / throw away servers in response to demand
which can be very spikey. <br>
<br>
The project broke my previous "personal best" for numbers of
concurrent servers in a single solution by about 750 ;) and I think
we may be one of very few companies to have persuaded Amazon Cloud
to return "Out of capacity" errors as opposed to "Exceeded account
limits"... <br>
<br>
The responsiveness of AWS is remarkable - without hot spares etc, we
can create and commission a server entirely from scratch less than a
minute after exceeding a load threshold.<br>
<br>
Adrian<br>
<small><b>Dr Adrian Roe<br>
Director</b></small><br>
<br>
On 12/02/12 19:26, Miles Fidelman wrote:
<blockquote cite="mid:4F38125A.6030806@meetinghouse.net" type="cite">Steve
Strong wrote: <br>
<blockquote type="cite">The largest the we have run at id3as so
far is 768 erlang nodes, distributed across 5 data centers. The
nodes were structured in a hierarchy and used the hidden flag to
ensure that the network did not become fully connected.
<br>
<br>
<br>
</blockquote>
cool! can you say a little more about what you were doing with
them? <br>
<br>
</blockquote>
<br>
</body>
</html>