java 内存测试,Java单元测试：如何测量方法调用的内存占用量

最新推荐文章于 2021-11-18 09:31:11 发布

Gyrolt

最新推荐文章于 2021-11-18 09:31:11 发布

阅读量279

点赞数

文章标签： java 内存测试

本文探讨了如何确保一个执行大量处理并操作多个集合的Java类不会导致内存溢出。提出了几种可能的解决方案，包括通过微基准测试估算内存需求、基于启发式方法构建分配策略、利用Guava的缓存实现基于内存的驱逐策略，以及编写基准测试来测量内存分配。此外，还介绍了使用System.gc()和内存计算来粗略估计方法的内存占用。

摘要由CSDN通过智能技术生成

Assuming I have a class that does some heavy processing, operating with several collections. What I want to do is to make sure that such operation can't lead to out-of-memory or even better I want to set a threshold of how much memory it can use.

class MyClass()

{

public void myMethod()

{

for(int i=0; i<10000000; i++)

{

// Allocate some memory, may be several collections

}

class MyClassTest

{

@Test

public void myMethod_makeSureMemoryFootprintIsNotBiggerThanMax()

{

new MyClass().myMethod();

// How do I measure amount of memory it may try to allocate?

}

What is the right approach to do this? Or this is not possible/not feasible?

解决方案

I can think of several options:

Finding out how much memory your method requires via a microbenchmark (i.e. jmh).

Building allocation strategies based on heuristic estimation. There are several open source solutions implementing class size estimation i.e. ClassSize. A much easier way could be utilizing a cache which frees rarely used objects (i.e. Guava's Cache). As mentioned by @EnnoShioji, Guava's cache has memory-based eviction policies.

You can also write your own benchmark test which counts memory. The idea is to

Have a single thread running.

Create a new array to store your objects to allocate. So these objects won't be collected during GC run.

System.gc(), memoryBefore = runtime.totalMemory() - runtime.freeMemory()

Allocate your objects. Put them into the array.

System.gc(), memoryAfter = runtime.totalMemory() - runtime.freeMemory()

This is a technique I used in my lightweight micro-benchmark tool which is capable of measuring memory allocation with byte-precision.