MIAMI -- A Wendy's manager was shot in the arm over chili sauce -- and police in Miami are looking for the shooter.

Police said a man in the drive-through argued with an employee because he wanted more packets of the condiment. The worker told the customer that restaurant policy prohibited a customer from getting more than three packets.

The customer demanded 10 and got them. Police say the man then asked for even more and the manager came out to talk to him.

Miami-Dade police spokeswoman Mary Walter said that's when the manager was shot several times in the arm, but didn't suffer serious injury.

The victim was taken to the hospital with non-life-threatening injuries.

Police are still searching for the chili sauce shooter, who drove off with a woman in his car.

As I mentioned in my review of the Sun X2200 M2 servers we got recently, which we absolutely loved, Sun’s storage wasn’t impressive at all. In fact, it was downright bad. But before I get into the gory details, I feel compelled to mention that I believe Sun’s future, including storage, is bright. Their servers rock, they’re innovating all over the place, and for the most part, the people at Sun have been fantastic to work with - even when they’re being told their storage hardware sucks. That’s impressive. Now, on with the show:

The storage arrays I’m blogging about here are Sun StorEdge 3320 SCSI arrays. For more on why we chose this particular model, you can read about my on-going search for The Perfect DB Storage Array. The bottom line, though, for us is that Speed Matters. Their list price is quite expensive, but Sun was willing to work with us on the price, and we managed to get things into a reasonable ballpark. Reasonable, that is, as long as they performed.

First, some details. These boxes were destined to be part of our DB layer, with the first few going in as new storage for replication slaves. The goal was to maintain a high number of small (4K) i/o operations per second (IOPS) with an emphasis on writes, since scaling reads is easier (add slaves) than scaling writes (only so many spindles you can add, etc). In this particular case, the writes were being delivered from a MySQL master using InnoDB running Linux on 3 effective 7200rpm spindles, so the Sun array, on paper, should be able to keep up, no sweat. If your needs differ, our story might not be useful - test for yourself.

Installing and configuring them was an adventure. Craig Meakin, our Server Surgeon, was tasked with installing them and immediately ran into a snag. When configured for DHCP management access (which is how they were set up out of the box, exactly how we like them), they wouldn’t actually DHCP an IP address. It took someone at Sun wading through 4 different manuals to determine that not only did the array have to toggled to DHCP, but you also had to write “DHCP” in the IP address spot to make it work. Strike one.

(As an aside, one of Sun’s engineers also told us, after we’d bought them and installed them in the rack, that these storage arrays don’t come with battery backed write caches. Given how expensive they are, I was shocked and furious, but quickly got verification that they do, indeed, have BBWC.)

We brought one online and moved a DB slave snapshot over which was a few hours out-of-date and started replication so it could catch up with the master. Obviously, it wasn’t live and in production, so it was mostly spooling and committing writes from the master, only doing reads as needed for updates and whatnot. A very light load, in other words. With interest, we started timing how fast it would catch up, since it should scream. We were betting at least 2X (15K drives, after all) faster than the master, and on par with our other 15K SCSI slaves. Instead, we measured more than 4X *slower* than our slaves. Strike two.

Ok, no worries. Obviously this is a new array, and we did something terribly stupid setting it up. Sun support to the rescue, right? So we opened up tickets, dumped our config and all other relevant details to them. Nada. Oh, they came back with lots of suggestions and things to try. But none of them helped. Next step was to grab detailed system i/o statistics on production slaves which worked and Sun SE3320s that didn’t, so Sun could compare. And compare they did - their data showed a 6X performance differential between our production slaves (which had $700 off-the-shelf LSI SCSI MegaRAID cards in them) with 15K disks and Sun’s hardware. Sun was 6X slower. Final verdict? “System is performing as designed.” Strike three - they’re out!

Frantically, since the entire reason we had gone with Sun was because Rackable had shipped us a bunch of broken units and we were now months behind on an expansion project, we called Dell and ordered some PowerVault MD3000 SAS arrays. I always give Dell props for fast, efficient delivery, and knock them for a lack of innovation. In this case, they not only got us the gear fast, but the MD3000 turned out to be a fantastic DAS device and nearly perfect for our needs. Thank goodness!

Normally, that would be the end of our little tale, but as luck would have it, when Sun realized they’d laid an egg with the SE3320, they rushed us an engineering sample of their not-yet-announced (then) new StorEdge 2540 array. The good news? It performed neck-and-neck with the Dell array and uses SAS drives, which we prefer over SCSI. The bad news? They weren’t out yet and we needed storage yesterday. I believe they are out now, and I would buy the 100% SAS version, the StorEdge 2530, rather than 2540, for use in our datacenters if we hadn’t gotten the Dells.

So now we’ve got fantastic Sun servers attached to fantastic Dell storage. And our little franken-servers are as happy as can be. Fast, too.

Sometimes even without my having seen Albertine again, without anyone’s having spoken to me about her, there would flash from my memory some vision of her with Gis?le in an attitude which had seemed to me innocent at the time; it was enough now to destroy the peace of mind that I had managed to recover, I had no longer any need to go and breathe dangerous germs outside, I had, as Cottard would have said, supplied my own toxin. I thought then of all that I had been told about Swann’s love for Odette, of the way in which Swann had been tricked all his life. Indeed, when I come to think of it, the hypothesis that made me gradually build up the whole of Albertine’s character and give a painful interpretation to every moment of a life that I could not control in its entirety, was the memory, the rooted idea of Mme. Swann’s character, as it had been described to me. These accounts helped my imagination, in after years, to take the line of supposing that Albertine might, instead of being a good girl, have had the same immorality, the same faculty of deception as a reformed prostitute, and I thought of all the sufferings that would in that case have been in store for me had I ever really been her lover. One day, outside the Grand Hotel, where we were gathered on the front, I had just been addressing Albertine in the harshest, most humiliating language, and Rosemonde was saying: “Oh, how you have changed your mind about her; why, she used to be everything, it was she who ruled the roost, and now she isn’t even fit to be thrown to the dogs.” I was beginning, in order to make my attitude towards Albertine still more marked, to say all the nicest things I could think of to Andr?e, who, if she was tainted with the same vice, seemed to me to have more excuse for it since she was sickly and neurasthenic, when we saw emerging at the steady trot of its pair of horses into the street at right angles to the front, at the corner of which we were standing, Mme. de Cambremer’s barouche. The chief magistrate who, at that moment, was advancing towards us, sprang back upon recognising the carriage, in order not to be seen in our company; then, when he thought that the Marquise’s eye might catch his, bowed to her with an immense sweep of his hat.