How much time commitment do you figure on when your site is down and paying customers are calling and emailing you?
2,377 karma · joined September 25, 2009
I have an ancient quad-900Mhz Xeon with 6GB RAM (customer does not want to migrate) that has an uptime of 1600 days, and for which total network issues during that period was a few hours (wonky power to switch).
Cloud is too often comparable to "vapor" in terms of the claims of redundancy and availability.
You can see the timeline here: http://en.wikipedia.org/wiki/Rhapsody_%28operating_system%29
Rhapsody was the first OSX.
May I ask, have you ever used a NS3.3 or 4.2 based system for any length of time?
Quartz is basically "Display PDF" instead of "Display PostScript" with the architectural difference being that DPS was client-server, with bits of PostScript being interpreted on the fly; while Quartz got rid of the round trips between client and server, merging everything into one faster, monolithic layer. I recommend you look at the PS and then the PDF specs, they are about 90% identical.
The code imported from MacOS also ran in a separate "box" on top of the lower-level details.
Really the best case I can make for my argument is to point out the similarity between NeXTStep's IOKit drivers and the OSX IOKit drivers. That is the part, that really DOES interface with the guts of the system.
NeXTStep ran on PA-RISC, Intel x86, Motorola 68K and SPARC architectures since well before 2000. Rumors of ports to other platforms such as DEC Alpha, MIPS, etc. were also around, but I have no idea whether or not this ever happened.
Supposedly Jobs had a "NRW" the NeXT RISC Workstation, which was a Motorola 88K based system running NeXTSTep, on his desk for quite some time. I have no way of knowing how true this. see http://en.wikipedia.org/wiki/Motorola_88000
See: http://en.wikipedia.org/wiki/High_availability#Percentage_ca... for a handy chart and follow along with any of your favorite *aaS providers!
Full virtualization like KVM or VMWare, require you to give each VM extra RAM for use with disk cache. For instance, if you had a typical set of processes that used 1.5GB, and you gave it 1.7GB, that would hardly be enough, as you want more than 200MB of disk cache.
Under LXC and OpenVZ, any unused RAM becomes globally available for disk caching, giving a decent performance boost and further reducing the resouce commitments per-VM.
One example: a customer had some lousy queries in their SQL, but they really needed to have a good demo of their site. We moved them to a 32GB RAM system and gave the container 8GB.
As a result, nearly the entire 20GB database (or at least the parts that were needed), got loaded into the disk cache after the first batch of queries were run. It was enough to get them over the hump (they later figured out the nasty SQL that was getting them in trouble) and they had a good demo. After that, we live-migrated back to their regular server.
Maybe he should refuse money from such companies? (will not happen of course!)
Web and email servers that are publicly accessible, and your desktop or laptop that you connect at home or at a Wifi point, will probably still be IPv4.
IPv6 will be used internally by large companies, by large DSL ISPs and Comcast, but the interface the end-user will see, will be IPv4.
I think 99% of the usage will occur in non-visible ways - Comcast will have all their home-subscriber modems put out IPv4 on the side you see, but v6 on the pieces you don't, such as the management interface that lets them remotely configure and manage your modem.
Combined with large 6to4 gateways they will run on their edge (where they connect with non-v6 enabled systems), most people will not really notice anything.
The tipping point will come, but not for another 5 years I think, that is, 2 more hardware upgrade generations.
Mobile of course, will go to v6 first, since no-one cares as to how their phone accesses the web.
They made all kinds of films used for imaging various parts of the spectrum, and would have had their researchers available for the USG (surely at a price of course). That they had fissionable material is entirely reasonable and expected.
"Our ancestors... possessed a right, which nature has given to all men, of departing from the country in which chance, not choice, has placed them, of going in quest of new habitations, and of there establishing new societies, under such laws and regulations as, to them, shall seem most likely to promote public happiness"
(purely a guess based on anecdotal evidence ... the only guy I know with a Cadillac STS was a guy who only has high school and was a well-compensated salesman; but even he is now driving Audis)
Anyone familiar with telecom and living in PA, WV, other states that have Verizon as the ILEC, knows this.
You place a bunch of solar panels in a sunny place that also has water.
Then you directly power the grid when it is sunny and all power is needed.
When not needed, you power the catalyst, storing the hydrogen.
When it is dark, you use the hydrogen to create power and (maybe) heat.
And then quietly replace it (after dumping the config and replicating the configuration) with a $100 half-depth Supermicro server bought off Ebay, running OpenBSD?
And then walk out, like the Grinch after he artfully puts Cindy Lou Who to bed, with a nice new 3945 for my own use?
EDIT: forgot to mention, I need a CF card reader also to get the config off the Cisco flash.