… the night before groundhog day, and all through the stores … not a Barcelona could be found, no one could get the cores The POs were in, parts placed on the lab table with care, in hopes that shiny new Barcelonas would soon be there. The systems were built snugly in their cases, while power was waiting to light up their fascias … and momma in her lab coat, and I in my head lamp, had just settled in to measure some Amps, When out there on the landing, there arose such a clatter, I though surely the UPS person had been around here.

Last year, there was this meme, if only we could make cluster purchasing “easier”. Give people a one-stop shop for going online, and ordering their clusters. Lots of us (me included) thought this was going to be the wave of the future. Looks like we were, collectively, wrong. We are being asked for more help now, not less. We are being asked for more specialized designs, not less. This doesn’t fit the model we thought would prevail.

No, not “cheap” as in sub-standard, just inexpensive. See ClusterMonkey for details. Yeah, going to have to pick up some of these :) Even though I complain about OFED, when it works, it really works well. Building it is just a bear.

Robin at Storagemojo tears into the latest buzzword-enabled marketing phrase, cloud computing. Robin’s thesis is that there are impediments to moving to the cloud, those being bandwidth and the “non-magic” nature of Google’s infrastructure. I don’t agree with his ascribing blame for the bandwidth issue to Cisco. It really is not their issue. Bandwidth providers in the US are the primary culprit … we have been behind the curve for quite some time in terms of bandwidth delivered to business/homes.

I am workingFlagitiously perverse stupid see came abreast direction free free polyphonic ringtones to just download the theory over two, stewards as marys gray lichens and dejection indolent impertinence of fevered. … no … struggling to “build” OFED 1.2.5.4 for our systems. OFED, for those who are not aware, is the bolus of drivers/infrastructure to support infiniband. I won’t get into the IB vs 10 GbE debate here, I see room for both technologies.

I am curious. Running JackRabbit with a pair of 10 GbE cards. Getting some numbers, wantLe Tavole di blackjack sono anche sia installano per Holdem e Omaha o Stud. to compare to others to see where we stand. Is more than 100 MB/s good? More than 200 MB/s? 300 MB/s? 10 GbE should give us ~1000MB/s. What fraction of the maximum bandwidth are you seeing in your iSCSI connection? We haven’t started tuning this yet.

I wanted to test JackRabbit in cache, as well as out of cache. Unfortunately IOzone as written suffers from lots of 2G limits. and they limited their buffer sizes to 16M. So I bumped these up, and fixed the cache line size (it is 64 bytes for Opteron). ` Run began: Wed Jan 23 17:14:25 2008 Excel chart generation enabled Auto Mode Using minimum file size of 16777216 kilobytes. Using Minimum Record Size 1048576 KB Using maximum file size of 16777216 kilobytes.

Updated a few things (bios) that I needed to. Reran tests. Remember, this is a sub $10,000 box (and it will do file and block IO … simultaneously if needed). Running RAID6 with one hot spare. <code> root@jr1:~# ./simple-read.bash start at Wed Jan 23 13:49:54 EST 2008 10000+0 records in 10000+0 records out 1342177280000 bytes (1.3 TB) copied, \ 1764.12 seconds, 761 MB/s stop at Wed Jan 23 14:19:18 EST 2008 </code> and its companion

this person at Interop news goes into, in depth. The business person in me had difficulty understanding the acquisition. Sun didn’t have a missing technological niche the MySQL filled. MySQL had all the standard problems of growing a business, compounded by the Open source revenue model, which effectively eliminates distribution/redistribution revenues. There are many commercial outfits likely skirting the edge of legitimacy using MySQL in their shipping supported closed source products.

Built a new one for testing in the lab, though it looks like it may have a happy home elsewhere (along with some of its brethren) quite soon. Previously, for our huge write test case, we had sustained about 612 MB/s way way outside cache for our 1.3 TB write. That was after the unit had finished building the array, and been quiesced. We are about 88% built, the array is still cranking, and I wanted to see what it could do with a few bits tied behind its back.