ABSTRACT
Applications often have large runtime memory requirements. In some cases, large memory footprint helps accomplish an important functional, performance, or engineering requirement. A large cache,for example, may ameliorate a pernicious performance problem. In general, however, finding a good balance between memory consumption and other requirements is quite challenging. To do so, the development team must distinguish effective from excessive use of memory.
We introduce health signatures to enable these distinctions. Using data from dozens of applications and benchmarks, we show that they provide concise and application-neutral summaries of footprint. We show how to use them to form value judgments about whether a design or implementation choice is good or bad. We show how being independent ofany application eases comparison across disparate implementations. We demonstrate the asymptotic nature of memory health: certain designsare limited in the health they can achieve, no matter how much the data size scales up. Finally, we show how to use health signatures to automatically generate formulas that predict this asymptotic behavior, and show how they enable powerful limit studies on memory health.
- G. Ammons, T. Ball, and J. R. Larus. Exploiting hardware performance counters with flow and context sensitive profiling. In Programming Language Design and Implementation, pages 85--96, 1997. Google ScholarDigital Library
- J. Berdine, C. Calcagno, B. Cook, DDistefano, P. W. O'Hearn, T. Wies, and H. Yang. Shape analysis for composite data structures. Technical Report MSR--TR-2007-13, Microsoft Research, 2007.Google ScholarCross Ref
- S. M. Blackburn and et. al. The DaCapo benchmarks: Java benchmarking development and analysis. In OOPSLA '06: Proceedings of the 21st annual ACM SIGPLAN conference on Object-Oriented Programing, Systems, Languages, and Applications, New York, NY, USA, Oct. 2006. ACM Press. Google ScholarDigital Library
- M. D. Bond and K. S. McKinley. Bell: Bit-encoding online memory leak detection. In Architectural Support for Programming Languages and Operating Systems, pages 61--72, 2006. Google ScholarDigital Library
- A. B. Brown, A. Keller, and J. L. Hellerstein. A model of configuration complexity and its application to a change management system. In Integrated Management, 2005.Google Scholar
- T. H. Cormen, C. E. Leiserson, R. L. Rivest, and C. Stein. Introduction to Algorithms. MIT Press and McGraw-Hill, second edition, 2001. Google ScholarDigital Library
- P. N. de Souza, R. J. Fateman, J. Moses, and C. Yapp. The Maxima Book, 2004. http://maxima.sourceforge.net.Google Scholar
- B. Dufour, K. Driesen, L. J. Hendren, and C. Verbrugge. Dynamic metrics for java. In Object-oriented Programming, Systems, Languages, and Applications, pages 149--168, 2003. Google ScholarDigital Library
- GNU Trove: High performance collections for Java. http://trove4j.sourceforge.net.Google Scholar
- M. J. Harrold, G. Rothermel, R. Wu, and L. Yi. An empirical investigation of program spectra. In SIGPLAN/SIGSOFT Workshop on Program Analysis For Software Tools and Engineering, pages 83--90, Montreal, Canada, June 1998. Google ScholarDigital Library
- R. Hastings and B. Joynce. Purify-fast detection of memory leaks and access errors. In USENIX Proceedings, pages 125--136, 1992.Google Scholar
- S. Holzner. Eclipse. O'Reilly Media, Inc., first edition, Apr. 2004.Google Scholar
- M. Jump and K. S. McKinley. Cork: dynamic memory leak detection for garbage-collected languages. In Symposium on Principles of Programming Languages, pages 31--38, 2007. Google ScholarDigital Library
- M. R. Lyu, editor. Handbook of Software Reliability Engineering, chapter 9 (Orthogonal Defect Classification). IEEE Computer Society Press, 1995.Google Scholar
- N. Mitchell. The runtime structure of object ownership. In The European Conference on Object-Oriented Programming, volume 4067 of Lecture Notes in Computer Science, pages 74--98. Springer-Verlag, July 2006. Google ScholarDigital Library
- N. Mitchell and G. Sevitsky. Leakbot: An automated and lightweight tool for diagnosing memory leaks in large Java applications. In The European Conference on Object-Oriented Programming, volume 2743 of Lecture Notes in Computer Science, pages 351--377. Springer-Verlag, July 2003.Google ScholarCross Ref
- N. Mitchell, G. Sevitsky, P. Kumanan, and E. Schonberg. Data structure health. In International Workshop on Dynamic Analysis, Minneapolis, Minnesota, United States, May 2007. Google ScholarDigital Library
- N. Mitchell, G. Sevitsky, and H. Srinivasan. Modeling runtime behavior in framework-based applications. In The European Conference on Object-Oriented Programming, volume 4067 of Lecture Notes in Computer Science, pages 429--451. Springer-Verlag, July 2006. Google ScholarDigital Library
- S. Pheng and C. Verbrugge. Dynamic data structure analysis for java programs. In International Conference on Program Comprehension, June 2006. Google ScholarDigital Library
- D. Rayside, L. Mendel, and D. Jackson. A dynamic analysis for revealing object ownership and sharing. In Workshop on Dynamic Analysis, 2006. Google ScholarDigital Library
- R. Shaham, E. K. Kolodner, and M. Sagiv. Automatic removal of array memory leaks in java. In Computational Complexity, pages 50--66, 2000. Google ScholarDigital Library
- Java 2 Platform, Enterprise Edition. http://java.sun.com/j2ee.Google Scholar
- Quest Software. JProbe® Memory Debugger. http://www.quest.com/jprobe, 2005.Google Scholar
- SPEC Corporation. The SPEC JVM Client98 benchmark suite. http://www.spec.org/osg/jvm98, 1998.Google Scholar
- Yourkit LLC. Yourkit profiler. http://www.yourkit.com.Google Scholar
- T. Xie and D. Notkin. Checking inside the black box: Regression testing based on value spectra differences. In International Conference on Software Maintenance, pages 28--37, Chicago, Illinois, Sept. 2004. Google ScholarDigital Library
- T. Yang, M. Hertz, ED. Berger, S. F. Kaplan, and J. E. B. Moss. Automatic heap sizing: Taking real memory into account. In International Symposium on Memory Management, 2004. Google ScholarDigital Library
Index Terms
- The causes of bloat, the limits of health
Recommendations
The causes of bloat, the limits of health
Proceedings of the 2007 OOPSLA conferenceApplications often have large runtime memory requirements. In some cases, large memory footprint helps accomplish an important functional, performance, or engineering requirement. A large cache,for example, may ameliorate a pernicious performance ...
Automatic detection of memory anti-patterns
OOPSLA Companion '08: Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applicationsIn large distributed enterprise systems detection of memory problems can be a burdensome task. For understanding the memory related problems a catalog which documents memory anti-pattens is proposed. This paper also introduces our proposed prototype ...
Methodology for Refinement and Optimisation of Dynamic Memory Management for Embedded Systems in Multimedia Applications
In multimedia applications, run-time memory management support has to allow real-time memory de/allocation, retrieving and processing of data. Thus, its implementation must be designed to combine high speed, low power, large data storage capacity and a ...
Comments