Earlier quoted context omitted.
I am pretty sure he meant 2600Hz anyway Besides everyone knows, nobody whistles 2600Hz, they just get the toy out of the Cap'n Crunch box to do it for them. http://en.wikipedia.org/wiki/John_Draper#Phreaking
Well, no. It was a joke, so it was 2600 baud, not Hz.
Tell HN: Server Status
121–124 of 124 posts
Re: Tell HN: Server Status
#122The trend I'm noticing is people mentioning that if only HN was moved to , problems would go away. Instead of doing that, they probably dropped a bit more than a thousand dollars on a box, and are probably saving thousands in costs per year. This is money coming out of someone's pocket. This site is here, and it's a charity, being provided free of cost, to you. Who cares if HN is down for a few hours? Seriously? Has…
HN is not a charity, it is a marketing platform for YC with some community aspects. There is a very strong bias to everything YC. The HN community has also outgrown the software HN was built on you can see this in threads like: https://news.ycombinator.com/item?id=7051091 but even that thread is an extreme many front page items that gain traction are hard to go through because of things like lack of foldable comments…
Re: Tell HN: Server Status
#123I'm sure it has been asked many times before, but I'd love to hear the latest thinking... Why in 2013 is HN still running on bespoke hardware and software? If a startup came to you with this sort of legacy thinking you'd laugh them out of the room.
If HN was on AWS, where would we go to discuss AWS outages?
This doesn't explain the penny-wise (IMO) allocation of hardware or dev/sysadmin resources of course.
Re: Tell HN: Server Status
#124Earlier quoted context omitted.
Reading 2 disks is not very much slower than 1. Its always the I/o bandwidth that is at issue, so it very much depends on the connectivity. And it all pretty much impacts your customer. We've all suffered under the 4-hour mirror rebuild, the whole machine made inoperable by the constant disk load. The only way to alleviate that, is to design extra bandwidth (e.g. another cable and controller) that's used exclusively…
Can you elaborate on the second controller? Are you referring to two disks on two controllers, using mdadm (or similar) to create a software RAID 1 across the two?