I was … but then it was determined that I needed to be giving 2 of the STAC summit talks in Chicago and NY on the day jobs’s systems. Then this week, Tianhe-2 info came out, and … well … WOW! Great job guys! (ob-day job: “could we interest you in some monsterously fast storage to go with that space-time fabric warping super?") I was speaking recently with a VC we had talked to in early 2002 about accelerators.

Got confirmation from marketing folks that I won’t cause irreparable damage if I just put the link up. Next week. Early.

See here: ( http://scalableinformatics.com/blog/ ) The way I looked at it, I needed a place to talk more product/solutions/work without having my own personal opinions on myriads of things weave throughout. That is, scalability.org is something of mine personally, that I write for, based upon whatever itch I wish to scratch. The blog at the day job lets us (collectively) talk about cool things without having that “me/mine” thing intermix. I’ll be updating here of course as well.

I can’t talk publicly about everything yet, just its been so demanding of my time. I’ve run and debugged benchmarks, flown in to meet customers and others, generated many quotes, given many presentations. In this, I’ve got two hard deadlines for getting stuff written that I have to do before I can write anything here. So let me crank on those in the next 24 hours, and I’ll update.

Here in the US, we have a number of scandals brewing. Many of those for the party in control of the White House and the Senate would like to have you believe that these are in fact tempests in teapots. In this case, there are at least 2 Nixonian scandals going non-linear here, with a 3rd trying to break through. The political left is doing all it can to wave off one of them, though this is getting progressively harder by the day as more information comes out.

Imagine you have some … I dunno … gargantuan amount of bandwidth available, to and from your disks. And you have just positively insane IOP rates, at these very high bandwidths. And then you tightly couple a few hundred processor cores, and a few terabytes of memory. What would you consider “gargantuan” bandwidth? What would you consider “insane” IOP rates? And most importantly, if you had the type of IO fire power you considered gargantuan and insane, what would you do with this?

Take a gander. Some things are missing, and our marketing folks are developing the content where needed, and revising it where we have existing content. Its quite refreshing to see this. It will get better over time. Its running in our facility now, and likely we’ll have a few clones in the cloud as well. But thats for later.

Who’da ever thunk that MD simulations would start to become large enough to present IO and analysis problems? Way way back when the digital supercomputing dinosaurs roamed the earth, looking for problems to crunch on, I simulated gallium arsenide on some of these machines. I’d be lucky to get 100 time steps done, in a week, for 64 atoms. 64 atoms in double precision, with position, velocity, and atom type, lets be generous and call this 64 bytes in binary or 80 bytes, one terminal line, per atom in text.

Yes, actually we do. Too many. Turns out that little law of supply and demand does in fact hold true. The higher the demand for something in limited supply, the higher the price (wages) you will pay for it. By applying forces to this law, you impact a number of outcomes. That is, if you start monkeying around with the supply, sure, you can adjust the price you pay for the STEM.

In short, I am trying to verify what we measured. Its repeatable, I’ve been measuring it for a week now, and having trouble with it, but I want to make absolutely sure I get this correct. Because these are big numbers. Very. Very. Big. It would be annoying if I made a mistake. So I am double/triple/quadruple checking.