Helping ordinary people create extraordinary websites!
| |
Helping ordinary people create extraordinary websites! |
Eye on Performance: Profiling on the EdgeBy Jack Shirazi & Kirk Pepperdine2005-04-21 
Simple But Ugly
These are simple techniques, but they are not hugely productive. We would have much preferred to use a full-featured profiler to get the data out, especially because they present data in ways that make analysis much easier. We would have liked to have viewed the heap from its roots and tracked down the bigger sections until we found objects that referenced a lot of the heap, but we didn't have that option. The techniques we used were ugly compared to our normal tuning assignments. The result, though, was that we identified some objects that were completely unnecessary, that could be eliminated using a different implementation for some classes; and other objects that were necessary but that could be slimmed down or collapsed together to reduce their space requirements. As is often the case with object reduction, there was no one solution that could change our fat client to a slim one. As with people, dieting is hard work for Java applications, too! And just like dieting, it always seems to take longer than you'd like to lose that flab. Sadly, even the couple of hundred megabytes that we shaved off this client didn't leave it thin enough to run with a "real" memory profiler. Tutorial Pages: » What do you do When Your Tools are Too Fat? » A Trip to the Fat Farm » Back to the Beginning » Simple But Ugly » The Final Word » Resources First published by IBM developerWorks
|
 |