X-Git-Url: https://git.llucax.com/personal/website.git/blobdiff_plain/82c67a166ee0d3d8893c3ae1e84f91f067045fd0..026ddd134c2a47ab83069548c56f2e3d4cc04464:/source/blog/posts/2010/08/14-memory-allocation-patterns.rst

diff --git a/source/blog/posts/2010/08/14-memory-allocation-patterns.rst b/source/blog/posts/2010/08/14-memory-allocation-patterns.rst
index e5c79e6..c8d3442 100644
--- a/source/blog/posts/2010/08/14-memory-allocation-patterns.rst
+++ b/source/blog/posts/2010/08/14-memory-allocation-patterns.rst
@@ -27,13 +27,13 @@ affected by changes like `memory addresses returned by the OS`__ or by
 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
+__ https://www.llucax.com.ar/blog/blog/post/-7a56a111
+__ https://www.llucax.com.ar/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
+__ https://www.llucax.com.ar/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.
@@ -58,7 +58,7 @@ of the blocks). So the idea here is to measure two major things:
 * 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
+__ https://www.llucax.com.ar/blog/blog/post/250bf643
 
 I've selected a few representative benchmarks. Here are the results:
 
@@ -78,8 +78,7 @@ __ http://en.wikipedia.org/wiki/Barnes%E2%80%93Hut_simulation
 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
 
@@ -118,8 +117,7 @@ __ http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&art
 
 Here is the graphic summary:
 
-.. container::
-   :align: center
+.. container:: center
 
    .. image:: ##POST_URL##/14-memory-allocation/bigarr.rq.tot.png
 
@@ -150,8 +148,7 @@ __ http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&art
 
 Here are the graphic results:
 
-.. container::
-   :align: center
+.. container:: center
 
    .. image:: ##POST_URL##/14-memory-allocation/mcore.rq.tot.png
 
@@ -191,8 +188,7 @@ __ http://codepad.org/xGDCS3KO
 
 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
 
@@ -234,8 +230,7 @@ __ http://code.google.com/p/dil/
 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