Push the button, Frank.

uh, no, just the opposite. Many supercomputing applications are about getting access to compute/memory/io bandwidth with as little intermediation as possible. Job allocation methods on supercomputers typically allocate entire nodes, so the sort of fine grained prioritization is prescribed is rather irrelevant. Whole article looks a bit anachronistic, maybe it is sensible to people from a mainframe background where reliability/predictability trumps other requirements, but when performance is an important concern, this kind of intrusive over-monitoring described would not be wanted.

Given this problem, there are several options for fanout... Im assuming that hardware can be added, so adding a load balancer and then three or four machines to cope with the load behind the load balancer might be the quickest (least code change) way to address the issue. Especially if there is no global state needed, this is likely the most expedient.

An option that might be a bit more flexible on a single box, while still scalable, would be to have a task that parses each incoming job and posts it to a rabbitmq instance (AMQP bus.) rabbitmq works very well out of the box, with little tweaking. you then have the fifteen scripts called in subscriber instances as separate processes. You are essentially farming out all the IPC to the broker, and the broker does this sort of thing very well. The scripts are now isolated processes, and their memory management etc... now become separate issues (if one misbehaves, you an always have the subscription management wrapper around it restart it from time to time.)

Pika would be the preferred python bindings appropriate for speaking with the broker. You might still be beyond what can be done with a single node, but growing things with AMQP/rabbit is straight-forward.

Thanks for sharing... I think...

Get down and boogie and play that funky music till you die!

That's where I am too. I love the idea of smart watches, but I don't want anything clunky, or with poor battery life.

Simple notifications or apps (compass/GPS, weather, sunset/sunrise, heart rate monitor) that are useful when out and about, but not too clumsy on its tiny interface.

And ideally some sort of interoperability with various phones.

I don't have very high hopes of this type of device existing any day soon. So for now I'll stick with my Citizen WR200 atomic.

Yeah, in Vermont, it took all of about a year.

Vermont's state constitution forbids slavery and was adopted in 1777.

Several other rebel colonies declared themselves free even before independence was formally gained.

During the Revolutionary War, Britain transported slaves of loyalists to other British colonies. (The slaves were not emancipated.)

There was a British court decision in 1763, but it was not binding overall, seems to have been pretty widely ignored by other British courts at the time, and the matter would not be settled in the British Empire for several more decades.

You also managed to get both dates wrong. Nice going.

We don't actually have any sort of twilight this time of year in Stockholm, even though the sun does go down for about 5½ hours. It gets dark only if it happens to be cloudy between 2200 and 0330.

Not quite the midnight sun thing you hear about (that's further north), but it still takes some getting used to.

You really need some better reading material.

And you're THE ONLY ONE who can see this... right.

http://en.wikipedia.org/wiki/I...

Are you sure you were around 20 years ago? Mainstream/formula music has been around since the dawn of commercial audio recording. Blaming its existence on piracy is silly, and just makes you sound like a **AA shill.

No, they're reporting that it ran in the NYT, which is exactly what they're supposed to be doing.

I believe you intended to say "HTML isn't as popular a beverage".

I hate it when poor delivery spoils what would have been a good punch line.