How to counter premature optimisation
14213
Is optimisation the root of all evil - or, at least, many bugs There was a time in my career, in the 1960s, when optimisation wasn't optional. System memories were measured in kilobytes, instruction times in tens or hundreds of microseconds. We planned our programs around those limited resources.â¦
81452
The leading vendors in the data warehousing market are running scared of new entrants to the market that are offering data warehouse appliances (i.e. pre-integrated hardware, software, storage combinations) that can offer greatly superior performance at a significantly lower price.  In this white paper we will dispel the 'fog of war' that currently pervades the data warehousing landscape, dismissing those question marks that are irrelevant and gratuitous, but highlighting any genuine issues that need to be addressed.
235807
How to find the best choices in a crowded market.
86732
Why it fails to invest at the point of maximum optimism.
175387
On the Mark: The blame game within IT can slow the resolution of problems reported by end users. But there are tools that can put a stop to all the finger-pointing, Mark Hall writes.
87845
You say you want to remain cautiously optimistic. You have seen too many things over too many autumns so you are going to be patient and rational.
214617
Don't count on freezing eggs to offset a ticking biological&#13;&#10;clock just yet
225897
Irregular hors d'ouevres, scheduling mishaps, and the stockbroker's eternal dilemma.
254578
I love overclockers - I don&#39;t know if it&#39;s the nerves of steel needed to run components so far beyond their factory specifications that they need to be refrigerated, or the glowing water cooling pipes they use, or it might even be the UV lamps and dodgy
459255
If the load of application relies on incoming events, you may eventually face the happy curse of popularity: too much work to do with your available resources. If you set a limit on how many events you can process within a time period, you can avoid the flood. Vladi Belperchinov-Shabanski explains the algorithm and demonstrates working code.
196520
Relying on people to show up at a specific data center by a certain time to execute a recovery plan in the middle of a crisis reveals a certain lack of foresight. Consider an alternative -- keeping the lights on.
136881
Avoiding the false economy trap Reg Tech Panel â¦
302196
Avoid hot tips and invest like a master.
567861
Kernel development is getting faster, and testing has to keep up. This early warning tool gives developers insight into changes that could hurt performance.
290732
Learning from past mistakes and looking to future opportunities.
675185
In a new entry on his blog today, Marco Tabini introduces us to 5 PHP Performance Tips that we "probably don't want to hear".   I thought it might be interesting to write an article about the performance-enhancing tips you probably don't want to hear about - that is, those that are most likely to produce measurable (and durable) results but do require some effort on your part.   His list consists of:  You Don't Need To Plan Ahead In Order To Have A Plan Combat Database Abuse Do You Really Need A Database Anyway? Scale Horizontally Refactor To Scale Vertically  For each, he explains the title and gives a bit of validation to the point. There's some great mentions of tools that you can use to help accomplish them too - a profiler, the Lucene and Xapian full-text databases, and Lustre.
707034
The best strategies for coping with electronic overload.