some information about how much and what kind of memory are requested by the
different benchmarks.
-__ http://www.llucax.com.ar/blog/blog/post/-7a56a111
-__ http://www.llucax.com.ar/blog/blog/post/1490c03e
+__ /blog/blog/post/-7a56a111
+__ /blog/blog/post/1490c03e
I used the information provided by the ``malloc_stats_file`` CDGC__ option, and
generated some stats.
-__ http://www.llucax.com.ar/blog/blog/post/-2c067531
+__ /blog/blog/post/-2c067531
The analysis is done on the allocations requested by the program (calls to
``gc_malloc()``) and contrasting that with the real memory allocated by the GC.
* The extra amount of memory wasted by the GC when using precise mode because it
stores the type information pointer at the end of the blocks.
-__ http://www.llucax.com.ar/blog/blog/post/250bf643
+__ /blog/blog/post/250bf643
I've selected a few representative benchmarks. Here are the results:
Here is a graphic summary of the allocation requests and real allocated memory
for a run with ``-b 4000``:
-.. container::
- :align: center
+.. container:: center
.. image:: ##POST_URL##/14-memory-allocation/bh.rq.tot.png
Here is the graphic summary:
-.. container::
- :align: center
+.. container:: center
.. image:: ##POST_URL##/14-memory-allocation/bigarr.rq.tot.png
Here are the graphic results:
-.. container::
- :align: center
+.. container:: center
.. image:: ##POST_URL##/14-memory-allocation/mcore.rq.tot.png
Here are the graphic results for a run with ``-n 30000``:
-.. container::
- :align: center
+.. container:: center
.. image:: ##POST_URL##/14-memory-allocation/voronoi.rq.tot.png
Here are the results of a run of Dil to generate Tango documentation (around 555
source files are processed):
-.. container::
- :align: center
+.. container:: center
.. image:: ##POST_URL##/14-memory-allocation/dil.rq.tot.png