I have a new server up and running at new provider ReliableSite in New Jersey, but I've been looking for a second source because I don't want to have all my digital eggs in one basket.
Just got a too-good-to-turn-down offer at Incero in Dallas, and placed an order for three servers. They're smaller than the server I have at ReliableSite right now - 4 cores and 32GB vs. 16 cores and 64GB - but with the same disk space and less than half the price.
Two are general-purpose servers, with 2x2TB disks and 2x256GB SSDs in RAID-1; the third is a storage server with 4x2TB disks in RAID-5. These are just a 1ms ping away from the existing servers at SoftLayer in Dallas.
Oh, and each comes with 30TB of monthly bandwidth on a gigabit port, and a private back-end network.
The plan is to have two of these general-purpose servers in Dallas and two in New Jersey, replacing place of the current single larger server there. The four of them combined will cost about the same as our current main server. The new archive server costs about the same as our current archive server but has 50% more space, RAID-5, and eight times the RAM.
Resource
Before
After
Cores
12x2.93GHz
16x3.4GHz
Memory
24GB
128GB
Disk
4TB RAID-5
8TB RAID-1
SSD
64GB RAID-5
1TB RAID-1
Bandwidth
9TB
80TB
The new servers each have a four-core CPU, compared to our current dual-CPU 12-core system. But the new quad-cores are as fast as the older six-core chips, and we have twice as many of them in total, so we're doing pretty well there too.
In New Jersey we'll have Aoi and Midori; in Dallas, Akane and Mikan. Archive server will be Sakura. Our current high-bandwidth server, Kurumi, will be cancelled, since we have plenty of bandwidth on the new main servers and won't need it.
Once the migration is complete it will be cheaper than the existing servers and far more robust and flexible. If one server goes offline I'll be able to bring things right back up on another one; even if one entire datacenter goes down I'll have backups at the other site, and be able to get things up and running again pretty quickly.
Now I just need to work out how I'm going to use all this capacity. But that's a good concern to have.
Posted by: Pixy Misa at
11:41 AM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 402 words, total size 3 kb.
Sunday, September 09
Unicode 1F4A9!!!
My new cuss word.
Posted by: Pixy Misa at
07:59 PM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 6 words, total size 1 kb.
Friday, September 07
iPad Pre-review
That screen is beautiful. It's big enough for comfortable web browsing, when the Nexus 7 really isn't. Though for an IPS screen the viewing angles aren't that great - it loses clarity quite noticeably at even modest angles.
So far, I still prefer the (much cheaper) Nexus 7. It's much lighter (almost exactly half the weight), easier to navigate (physically, due to the smaller size), more comfortable to hold (the rubberised back makes a big difference), and much more responsive.
In particular, Google Play kills the App Store dead when it comes to performance. It can take several seconds for an app to start downloading on the iPad, and you just have to sit there and wait. If you try to select another app to download, it cancels the first request. The Nexus 7 lets you just go blip-blip-blip.
On the other hand, I have some much more featurey apps on the iPad, like GarageBand, ArtRage, and Pages. And I've finished my big bulk app install and won't need to go through that again for a while. We'll see how it holds up for doing actual work - I use the Nexus 7 for reading, playing games, and checking on things, but even answering email is a chore on a screen that small.
1
Thats odd. I've never noticed the itunes store acting that way. Purchases and updates have all run concurrently as far as I've experienced.
In truth, the 10" form factor has never been an issue. I can understand 7 being a little more convenient for maneuvering on a busy bus or train and stowing away when on the move.
I just wish for faster screen refresh on the iPad. Its a little laggy for ssh.
Posted by: Andrew at Sunday, September 09 2012 12:51 PM (Ob5uo)
2
Okay, maybe a network issue then. I'll see how it goes over the next few weeks.
As for the size and weight - the iPad is certainly much lighter and easier to hold than a notebook, but the Nexus 7 is so light that you don't notice the weight at all.
Posted by: Pixy Misa at Sunday, September 09 2012 04:33 PM (PiXy!)
Fire HD: 1280x800 7" IPS screen (matching the Nexus 7 and yesterday's Kobo announcement), microUSB and microHDMI.
16GB: $199
32GB: $249
Fire HD 8.9": 1920x1200 8.9" (surprise) IPS screen, microUSB and microHDMI.
16GB: $299
32GB: $369
Only dual-core CPUs instead of the Nexus 7's quad-core, but I don't know how much difference that will make for day-to-day use.
The Fire HD is 13.9 oz (394g) and the Fire HD 8.9" is 20 oz (567g). The Nexus 7 is a svelte 340g, but I don't think the extra couple of ounces on the Fire HD will hurt too much. The iPad is 662g, and let me tell you, it gets heavy after a while. (Pretty screen, though.)
Looks like a great launch: The $199 Fire HD provides twice the storage of the entry Nexus 7 but otherwise comparable specs (and HDMI output as a bonus). The Fire HD 8.9" is smaller and lighter than an iPad - and a lot cheaper at $299 vs. $499 for the entry model. You can get a 7" and an 8.9" and still have a dollar left over compared with the iPad.
Of course, Amazon is being Amazon, and we antipodeans aren't allowed to actually buy the damn things, but apart from that, it looks like a great launch. My best hope is that this will prod some of the other tablet companies into motion.
I just got my Fire a few months ago and already it's obsolete. Woe is me. (It's only a 1024*600 display, for one thing.)
I'm probably going to have to get one of these. I wonder how hard it will be to get all my books transferred over. Is it possible at all?
Posted by: Steven Den Beste at Friday, September 07 2012 11:09 AM (+rSRq)
2
If you got the books on Amazon, they should download straight to the device.
I'm using the Kindle App on my Nexus 7, and it has a "sync" option that goes and gets all my books (and my magazine subscriptions). On a real Kindle it's probably even easier.
Posted by: Pixy Misa at Friday, September 07 2012 11:22 AM (PiXy!)
3
When are the new units supposed to hit the street? I bought my Fire at my grocery/variety store (it's hard to explain Fred Meyer to someone who hasn't seen it) and I wonder when the new ones will come into stock.
Posted by: Steven Den Beste at Friday, September 07 2012 01:04 PM (+rSRq)
4
Sounds like the 7" version will ship this month, and the 8.9" model in November.
Posted by: Pixy Misa at Friday, September 07 2012 02:55 PM (PiXy!)
5CNet reports that ads are mandatory on all Fire HD devices now (my Fire is ad-free). I suppose you could always root it and install Fedora ARM release, but sheesh.
Posted by: Pete Zaitcev at Saturday, September 08 2012 07:34 AM (RqRa5)
6
Yeah, that's annoying, but it explains how they came in $50 cheaper than the Nexus 7.
Posted by: Pixy Misa at Saturday, September 08 2012 01:09 PM (PiXy!)
7
I noticed that the front page of amazon, introducing the fire hd's, now mentions future options for removing the ads. *censored* that, I'll wait until I can buy one without the ads at all.
Posted by: RickC at Sunday, September 09 2012 04:06 AM (WQ6Vb)
8
Edit link doesn't work on Chrome. Ignore that previous comment, I was wrong.
Posted by: RickC at Sunday, September 09 2012 04:07 AM (WQ6Vb)
9
Perhaps the Australian delay on the Fire HD is the 4G/LTE component. Negotiating a carrier deal or clearing the actual wireless components through Australian regulatory boards.
I wonder if this is going to put Google into a squeeze since their content store isn't a patch on Amazon's. I can see people going for the Fire as it has so much content available so easily, DRM concerns aside.
Posted by: Andrew at Sunday, September 09 2012 12:58 PM (Ob5uo)
Apple vs. Samsung - Wait A Minute. Strike That. Reverse It.
Previously in As the Worm Turns, we discussed how the jury in the case had ignored instructions from the judge and assessed damages to punish Samsung rather than to reflect actual financial harm upon Apple.
Now the jurors have opened their mouths again and demonstrated that they also ignored the judge's instructions on prior art, the key to Samsung's entire defence. That is, they made an error of law, rather than of fact.
The jury concluded that the prior art did not invalidate Apple's patents because the code would not run on an iPhone. Of course, the same argument would show that Samsung did not infringe on Apple's patents because their code won't run on an iPhone either.
And the judge specifically instructed the jury that this is not how prior art is evaluated. (Groklaw cite the relevant sections at the page linked above.)
Best quote:
I think he may have a valid point. Perhaps apple have invented some new numbers, like eleventy-four, that don't fit into the old computers properly due to magic and stuff.
1
Sounds like a monumental screwup. How did the jury end up making such a mess of it?
Posted by: Steven Den Beste at Thursday, September 06 2012 10:32 AM (+rSRq)
2
The guy with the most forceful personality was elected jury foreman, and when he acted like an expert, the others fell into line.
...then he decided to show his brilliance off to the public, too. Oops.
-j
Posted by: J Greely at Thursday, September 06 2012 11:06 AM (fpXGN)
3
And, somehow, it turned out that the jury foreman was someone who owned a software patent of, to put it bluntly, dubious validity. Massive screw-up by Samsung even having this guy on the jury at all, unless their Evil Secret Plan was to get the trial thrown out altogether on appeal (which, to be fair, has a pretty good chance of happening now?)
Posted by: Avatar_exADV at Thursday, September 06 2012 08:13 PM (GJQTS)
I think somewhere in the corporate offices of Apple and its lawyers, multiple voices are screaming every time the jury foreman appears in an interview, trying to get him to shut his mouth. It seems that every new interview conducted with the man since the verdict has seen him digging himself a deeper and deeper hole to drop into.
I do not believe the bad judgement of jurors is a crime, but this guy has been getting close to being a poster child for everything a juror can intentionally do wrong. Still not the worst examples available, but that is not a compliment.
Posted by: cxt217 at Friday, September 07 2012 06:47 AM (YM5S2)
Bad judgement by a juror is not a crime. But if it can be determined that he had a conflict of interest, and didn't say so when he was being questioned as a candidate, I think that is potentially a crime. (Perjury, if nothing else.)
I don't see how this leads to the whole case being dismissed, however. There is no "double jeopardy" rule in civil law.
Posted by: Steven Den Beste at Friday, September 07 2012 11:11 AM (+rSRq)
Delphi XE3 provides native support for Windows 7 & 8 (including what they're calling "Metropolis" this week), MacOS X, Android, and iOS.
Prism XE3 is ObjectPascal (the Delphi language) for .Net (Windows) and Mono (Linux and Mac). The language is largely the same, but the UI class library is different.
RemObjects Oxygene is Prism for .Net/Mono and WinRT (that is, Prism is Oxygene for .Net), Java (including Android, which runs almost-but-not-quite Java), and coming up to a beta release for "Nougat".
Only problem is, they hint but never explicitly say what "Nougat" is a code-word for. Apparently either MacOS X, iOS, or (most likely) both.
It's still messy, but probably the least messy solution for cross-platform native apps available today. And it's not horribly expensive. The Oxygene .Net/Java/Nougat bundle is $499; Delphi XE3 Professional is A$1169.
Assuming that Nougat covers all Cocoa platforms, that Oxygene bundle is perfect for me. One language lets me target the desktop on Windows 7 & 8 and Mac OS X, tablets and smartphones running iOS, Android, Windows Phone 7 & 8 and Windows RT, and servers running Java, .Net, or Mono. And I can easily embed Python and Ruby on the .Net/Mono and Java platforms (using IronPython, IronRuby, Jython, and JRuby respectively) to bring my existing code across. (Not sure about doing that with Nougat, though.)
One other interesting thing: With XE3 Embarcadero introduced a new EULA that forbade third-party (or indeed hand-rolled) client-server extensions for Delphi and C++ Builder Professional - you had to buy the 2x more expensive Enterprise or 4x more expensive Architect packages to do any client-server work at all. Since client-server architecture is universal these days - everything is client-server - this was unenforceable and frankly stupid.
The user forums erupted in protest.... And the offending EULA clause was pulled.
Posted by: Pixy Misa at
09:52 AM
| No Comments
| Add Comment
| Trackbacks (Suck)
Post contains 318 words, total size 3 kb.
Once upon a time I programmed in Progress. It was my database, my programming language, my query language, my display language, my database design tool, my search engine, and my text editor.
Not every change is for the better.
Case in point: Progress is now called Progress® OpenEdge® Advanced Business Language.
1
Wasn't aware of Xapian, looks fab as they used to say. The mix'n'match approach is kind of scary, leading to disparate systems with varying versions and dependencies. Always been a fan of The Monolith. Been developing my own monolith called Vermeer, but every year I start a new rewrite and so not very much gets released.
PS. Whenever I do a preview, it loses all the other form fields (name, email etc), one might even justifiably say for once it looses them. Very loose.
Posted by: Tombei The Mist at Tuesday, September 04 2012 12:14 PM (hGCqM)
2
Thing is.
Thats probably all that has changed with Progress. The naming. I don't think they've added anything substantial in some time.
Posted by: Andrew at Tuesday, September 04 2012 08:54 PM (Ob5uo)
3
Well, it depends on whether or not you consider "giving up on UI dev and promoting .Net" "substantial."
Posted by: RickC at Saturday, September 08 2012 08:28 AM (WQ6Vb)