CPP_CHEN的专栏

最近读了一些关于program performance的文章。结合自己的一些编程体会，总结如下。(1) Algorithm Complexity.一般情况，我们写代码首要的任务是要让它work，之后才考虑performance的问题。 但如果写代码的时候总是留意自己的算法不会是什么坏事，“不要进行不成熟的优化”，但也”不要进行不必要的劣化“是写代码时的一个很重要的守则.总是优先

敏捷软件开发原则，模式与实践书摘。拙劣设计的症状：僵化性(Rigidity)：很难对系统进行改动，因为每个改动都会迫使许多对系统其它部分的其它改动脆弱性(Fragility)：对系统的改动会导致系统中和改动的地方在概念上无关的许多地方出现问题牢固性(Immobility)：很难解开系统的纠结，使之成为一些可在其他系统中重用的组件粘滞性(Viscosity)：做正确的事情比做错误的事情要

http://highscalability.com/blog/2012/5/16/big-list-of-20-common-bottlenecks.htmlhttp://highscalability.com/blog/2012/2/27/zen-and-the-art-of-scaling-a-koan-and-epigram-approach.html

The Smallest Distributed SystemPosted on 18 Oct 2013 by Mathias MeyerTravis CI started out as an idea, an ideal even. Before its inception, there was a distinct lack of continuous integrat

Disclaimer: We always assume that when we have an issue and think it's the operating system, 99% of the time, it turns out to be something else. We therefore caution against assuming that the proble

Use this bidirectional, versatile method to pass data between kernel and user space.Due to the complexity of developing and maintaining the kernel, only the most essential and performance-cr

I joined LinkedIn about six years ago at a particularly interesting time. We were just beginning to run up against the limits of our monolithic, centralized database and needed to start the transition

Table of ContentsIntroductionSetting up the contextReproducing and understanding Linux's zone reclaim behaviorNUMA memory rebalancing also triggers direct page scansLessons learnedIntr