Posted by Coder.
May
31
Posted by Coder.
IBM developerWorks : Blogs : Software architecture, software engineering, and Renaissance Jazz
I am inside the ICU at Mayo clinic, just a few hours after my open heart surgery. Steve, my ICU registered nurse, is my eyes and fingers typing this blog. As you can tell by the very fact that I am blogging I am not dead yet.
Wishing you a speedy recovery.
May
31
Posted by Coder.
Stefan Kaes, author of the forthcoming book, “Performance Rails”, scheduled to publish in early 2007, has this to say about Rails performance …
InfoQ – Tracking change and innovation in the enterprise software development community
… [areas where] applications [fall] short of achieving good performance.
choosing a slow session container
doing things on a per request basis, which could have been done once at startup
repeating identical computations during request processing
reading too often and too much from the database (especially in conjunction with associations)
relying too …
May
26
Posted by Coder.
Eclipse Performance
…a collection of goofs, mistakes, and bad decisions made in developing plugins for the Eclipse platform. Many are standard Java programming problems, some are specific to Eclipse. The intent here is … to help other developers avoid similar pitfalls. The bloopers have been contributed from the community and may have been discovered in Eclipse SDK code or in third party plugins. Since all of Eclipse is implemented as plugins, the issues are usually generally relevant.
May
6
Posted by Coder.
Performance Tuning Best Practices for MySQL – Google Video
…where to best focus your attention when tuning the performance of your applications and database servers, and how to effectively find the “low hanging fruit” on the tree of bottlenecks. It’s not rocket science, but with a bit of acquired skill and experience, and of course good habits, you too can do this magic! [The talk is delivered by] Jay Pipes [who] is MySQL’s Community Relations Manager for North America.
May
4
Posted by Coder.
rchrd@Sun
If you can’t get your code over 90% parallelized, then you’d better pay attention to the part that is running in only one processor, and make sure that (serial) part is optimized. Because it will dominate performance.
May
2
Posted by Coder.
Optimization: Your worst enemy
Optimization is what you do when the performance is insufficient. Sometimes the optimizations are easy, sometimes they are hard. Sometimes they fly in the face of your original design, and sometimes they require that you grossly violate your beautiful abstractions in your class system. But always, and I repeat, always, my experience has been that no programmer has ever been able to predict or analyze where performance bottlenecks are without data. No matter where you …
Apr
17
Posted by Coder.
Jon Masamitsu’s Weblog
The amount of live data that is in the tenured generation is too large. Specifically, there is not enough free space in the tenured generation to support the rate of allocation into the tenured generation.
Apr
17
Posted by Coder.
Southern Storm Software, Pty Ltd
The libjit library implements Just-In-Time compilation functionality. Unlike other JIT’s, this one is designed to be independent of any particular virtual machine bytecode format or language. The hope is that Free Software projects can get a leg-up on proprietry VM vendors by using this library rather than spending large amounts of time writing their own JIT from scratch.This JIT is also designed to be portable to multiple architectures.
Apr
11
Posted by Coder.
Digg PHP’s Scalability and Performance – O’Reilly ONLamp Blog
Most scaling and performance challenges are almost always related to the data layer, and are common across all language platforms. Even as a self-proclaimed PHP evangelist, I was very startled to find out that all of the theories I was subscribing to were true. There is simply no truth to the idea that Java is better than scripting languages at writing scalable web applications. I won’t go as far as to say …
Apr
5
Posted by Coder.
Maoni’s WebLog
An absolute cricial thing to developing a server application is throttling. Unfortunately this is not known to everyone who develops server apps. Especially when developing managed server apps, some people think that GC should just take care of that aspect not realizing that GC manages memory, not requests. If your machine has 2GB of memory and each request takes 1MB of memory, it can’t handle more than 2048 requests concurrently. If you keep accepting requests as fast …