diff options
| author | aclement <aclement> | 2008-07-03 16:23:30 +0000 |
|---|---|---|
| committer | aclement <aclement> | 2008-07-03 16:23:30 +0000 |
| commit | a7e3927b1884823915020d2b3f7029507d60b790 (patch) | |
| tree | da35c2f0c148959eb171958a0de9c147ad9b0f58 /docs | |
| parent | 993e4b43af4a342f8060042000a67f0388f0d3fa (diff) | |
| download | aspectj-a7e3927b1884823915020d2b3f7029507d60b790.tar.gz aspectj-a7e3927b1884823915020d2b3f7029507d60b790.zip | |
1.6.1 final readme changes
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/dist/doc/README-161.html | 7 | ||||
| -rw-r--r-- | docs/dist/doc/memLtwStress_160.PNG | bin | 0 -> 50825 bytes |
2 files changed, 6 insertions, 1 deletions
diff --git a/docs/dist/doc/README-161.html b/docs/dist/doc/README-161.html index 35b58ea3b..e71b6643a 100644 --- a/docs/dist/doc/README-161.html +++ b/docs/dist/doc/README-161.html @@ -100,10 +100,15 @@ weaver instance correctly matched the lifecycle of the associated classloader. Here is a memory usage graph for AspectJ1.6.1 - this shows an application that spawns 7 threads which run continuously for a few minutes. Each thread repeatedly creates a classloader, weaves 500 classes using it then discards the classloader. You can see that over time the memory is recovered correctly and when all threads complete (and all classloaders are orphaned), all the weavers are discarded. + +<p>First, AspectJ 1.6.0, in which memory was never correctly recovered and so an OutOfMemory problem would always occur eventually. +<center> +<img src="memLtwStress_160.PNG"></img> +</center> +<p>And now AspectJ 1.6.1: <center> <img src="memLtwStress_161.PNG"></img> </center> -<p>In 1.6.0 the memory was never correctly recovered and so an OutOfMemory problem would always occur eventually. <h2>Incremental compilation</h2> diff --git a/docs/dist/doc/memLtwStress_160.PNG b/docs/dist/doc/memLtwStress_160.PNG Binary files differnew file mode 100644 index 000000000..dbf46c0fe --- /dev/null +++ b/docs/dist/doc/memLtwStress_160.PNG |
