サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
パリ五輪
blog.tsunanet.net
I recently did some work on some of our frontend machines (on which we run Varnish) at StumbleUpon and decided to track down some of the errors the Linux kernel was regularly throwing in kern.log such as:Feb 25 08:23:42 foo kernel: [3077014.450011] Out of socket memoryBefore we get started, let me tell you that you should NOT listen to any blog or forum post without doing your homework, especially
At StumbleUpon we've had a never ending string of problems with Broadcom's cards that use the bnx2 driver. The machine cannot handle more than 100kpps (packets/s), the driver has bugs that will lock up the NIC until it gets reset manually when you use jumbo frames and/or TSO (TCP Segmentation Offloading). So we switched everything to Intel NICs. Not only they don't have these nasty bugs, but also
That's a interesting question I'm willing to spend some of my time on. Someone at StumbleUpon emitted the hypothesis that with all the improvements in the Nehalem architecture (marketed as Intel i7), context switching would be much faster. How would you devise a test to empirically find an answer to this question? How expensive are context switches anyway? (tl;dr answer: very expensive) The lineup
You are a SVN user and you don't have time to learn new things, here is a 5min course to get started with Git and git-svn. Import your SVN repository in Git: git svn clone -s https://svn.foo.com/svn/projMake your own Git branch: git checkout -b work trunk git add the files you changed.git commitWant to sync with the remote master SVN repos? git svn dcommit There you go! And guess what, svn-wrappe
このページを最初にブックマークしてみませんか?
『blog.tsunanet.net』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く