Performance Anti-Patterns
Update: Follow-up Discussion on Artima
What and how should we be measuring? A good benchmark is:
Repeatable, so experiments of comparison can be conducted relatively easily and with a reasonable degree of precision.
Observable, so if poor performance is seen, the developer has a place to start looking. Nothing is more frustrating than a complex benchmark that [...]
Embedded.com - Using design patterns to identify and partition RTOS tasks: Part 1
… any operation whose deadline is measured in milliseconds—not microseconds—is a candidate for a high priority task. Assuming that your system has some serious computing to do at least once in a while, then anything that your system must do in milliseconds will [...]
10 Feb
Posted by coder as Architecture, Best practices, Java, Monitoring, Patterns, Performance, Processor, Profiling, Reliability, Scalability
Sun Dialogue Programs
(Q): If you have to pick top 10 things that you must monitor on any server to look for performance and/or scalability issues…what would they be?
Richard McDougall (A): Off the top of my head, in no particular order:
CPU: Check idle time and run queue length.
If there’s a CPU bottleneck, check if it’s an [...]
27 Jul
Posted by Coder as Patterns, Refactoring
Asked “What is Refactoring?” Martin Fowler answers “Refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior.”
Cyrus Najmabadi (developer at Microsoft) writes on his blog Cyrus’ Blather, “… if you perform an “extract method” of some code that sits in a tight [...]
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jul | ||||||
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 | |