DrJokepu on July 16, parent prev next [—]. A quick stylistical advice for you: calling someone you don't like or respect by his or her surname is just not very good manners and not very good style. If you want to express your antipathy in writing regarding the person you're writing about, call him Mr.
Smith or Mrs. Jameson and not Smith and Jameson - everyone will understand your feelings but you will still give them basic courtesy and respect, which, in turn, will make your readers take your writing more seriously. The funny thing is that I like the guy. I like both of them. I don't think that they are great hackers, but I enjoy reading their blogs and I respect their efforts. I also believe that StackOverflow is great. I tried contributing but almost always someone hits submit before I do so I gave up until I have more free time.
Sorry for not being politically correct, I thought this was HN. DrJokepu on July 16, root parent next [—]. Fair enough, I misunderstood what you meant then. I still don't think that using surnames only is a very nice thing, but maybe it's just me.
Jebdm on July 16, root parent prev next [—]. I read it the other way around. Calling somebody that you're not acquainted with by their last name in writing is pretty standard practice, and doesn't carry any connotations at least to me.
On the other hand, using a title like Mr. It's like saying "With all due respect, my good sir, you are incorrect". Obviously, YMMV. Jebdm on July 16, root parent next [—]. I like the Economist's style as well, mainly because it rings of old intelligence. But they have a large, overarching identity backing them, while as individuals most usually don't.
Similarly, they publish in a formal medium, which Hacker News is not. Huppie on July 16, parent prev next [—]. Joel is referring to his programmer s and I think Atwood is coding for StackOverflow. And what happens to the cache then? I think a key item in Stack Overflow's success is that they can predict with high reliability how big it will get. So when we reached a surprising dead-end in our quest to find a reverse proxy that could block HTTP clients using too much….
Our hosting provider, PEAK, let us know that they had a cooling compressor fail in the facility. The primary database server was apparently taken offline at AM Pacific Time by this thermal event.
Sure you do! It contained this paragraph: Michael spent some time doing a post-mortem, and discovered that the problem was a simple configuration problem on the switch. You can either set…. You may be wondering about the drastic ASP. Net reduction in processing time compared to which was hours despite 61 million more requests a day.
Besides replacing some servers and network gear, not much. What do we need to run Stack Overflow? We have unintentionally tested this, successfully, a few times. Since few systems exist in complete isolation and ours is no exception , architecture decisions often make far less sense without a bigger picture of how those pieces fit into the whole. Many subsequent posts will do deep dives into specific areas.
This will be a logistical overview with hardware highlights only; the next post will have the hardware details.
For those of you here to see what the hardware looks like these days, here are a few pictures I took of rack A it has a matching sister rack B during our February upgrade :. Finding us needs to be fast, so we farm this out to CloudFlare currently because they have DNS servers nearer to almost everyone around the world.
We peer with our ISPs using BGP fairly standard in order to control the flow of traffic and provide several avenues for traffic to reach us most efficiently.
I suppose this may be a good time to mention we have a 10Gbps MPLS between our 2 data centers, but it is not directly involved in serving the sites. We use this for data replication and quick recovery in the cases where we need a burst. But wait! Each of the sets mentioned earlier connects to the corresponding set in Colorado, and they load balance traffic between in the failover situation. We could make both sets connect to both sets and have 4 paths but, well, whatever.
Does it need SSDs? How much SSD capacity do we need? And should it be a 2-tier solution with HDDs as well? Is this data totally transient? Are SSDs without capacitors, which are far cheaper, a better fit? Will the storage needs likely expand? Is this a data warehouse type scenario? Are we looking at 3. If so, in a 12 or 16 drives per 2U chassis? Is the storage trade-off for the 3. Do we need to expose the disks directly?
Does the controller need to support pass-through? Memory: How much memory does it need? What must we buy? How much memory could it use? Do we think it will need more memory later? What memory channel configuration should we go with? Is this a memory-access-heavy application?
Do we want to max out the clock speed? Is it highly parallel access? Do we want to spread the same space across more DIMMs?
0コメント