![]() ![]() and Sridharan M., Thresher: Precise refutations for heap reachability, ACM SIGPLAN Notices ACM. et al., Profile-based pretenuring, ACM Transactions on Programming Languages and Systems (TOPLAS) 29( 1) ( 2007), 2. Blackburn S.M., Hertz M., Mckinley K.S.and Rajan V.T., A real-time garbage collector with low overhead and consistent utilization, ACM SIGPLAN Notices 38( 1) ( 2003), 285– 298. Aspect-Droid: Android App Analysis System, Proceedings of the Sixth ACM Conference on Data and Application Security and Privacy, ACM, ( 2016), pp. Ali-Gombe A., Ahmed I., Richard G.G., et al.The I/O overheads are about 28% and the total execution overheads are about 51% on average. ![]() By caching object access event in global register and removing redundant instrumentation, on Nexus7 and Android 6.0, the read/write barriers overheads of the profiler are about 19% on average for EEMBC, SciMark and other workloads. The Java object profiling mechanism proposed in this paper has low execution time overhead, imposes no overhead on the Java heap and does not modify any existing key data structure of the ART Virtual Machine, including the object layouts, class layouts and any others. The data profiled can help the developers to detect memory leaks, implement optimizations like pretenuring and tune the performance of garbage collector, etc. Our profiler records the allocation site, the class information of the object, the object size, the birth time and death time of the object, the physical memory trace of the object movements with time stamps, the last access time and the access regular pattern, etc., for every Java object. In this paper, we design and implement a novel and low-overhead Java object profiler based on the Address-Chain technique, on Android 6.0 and its ART virtual machine, which uses an AOT (ahead-of-time) compiler and has complex garbage collection algorithms. However, currently there lacks a low-overhead and efficient Java object profiler on Android and its Java virtual machines. Developers often use profilers to observe the utilization efficiency of Java objects, hoping to find out memory allocation bottlenecks, identify and solve problems such as memory leaks, etc. How to efficiently utilize Java heaps is one of the most important issues of concerns to the developers. Android systems typically run on resource-constrained hand-hold devices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |