[pypy-svn] r58072 - pypy/build/doc

[hpk at codespeak.net]

Author: hpk
Date: Thu Sep 11 19:04:57 2008
New Revision: 58072

Modified:
   pypy/build/doc/benchmark_memory.txt
Log:
some words regarding base interpreter size 
and that we want to mainly measure RAM usage 
caused by the app/benchmark. 



Modified: pypy/build/doc/benchmark_memory.txt
==============================================================================
--- pypy/build/doc/benchmark_memory.txt	(original)
+++ pypy/build/doc/benchmark_memory.txt	Thu Sep 11 19:04:57 2008
@@ -28,17 +28,22 @@
   apps (for cross-reference, e.g. to show the space-time
   trade-offs of the various GCs).
 
+
 Benchmark specifics
 --------------------
 
 * RAM usage: we need to refine what is exactly meant by this.
   An approximation is the amount of process-private RAM
   reported by the kernel.  See discussion below.
+  Also, we likely want to mainly measure the incremental 
+  RAM usage of a particular benchmark/app - i.e. the 
+  RAM that is used in addition to the bare interpreter 
+  loaded.   
 
 * GC microbenchmarks: allocating specific object types
   (strings/dicts/lists/tuples/old-style/new-style instances ...)
-  and scenarios like reading lines in large file.
-  (reuse some of the speed benchmarks?)
+  and little scenarios like reading lines from a large file.
+  also consider reuse some of the speed benchmarks. 
 
 * allocation patterns:
   1. allocate objects all the time, total number of objects
@@ -56,7 +61,7 @@
   - high-res sampling (either in the real system or in
     emulators, e.g. look at valgrind tools).
 
-* The "percieved pause" is probably best approximated by
+* The "perceived pause" is probably best approximated by
   the time it takes to perform a single collection.  For
   generational GCs we should measure the time of the
   collections of various levels; for example, nursery-only
@@ -76,7 +81,11 @@
 * pypy-c --opt=3 (for comparison purposes)
 
 We want to select and optimize good underlying settings for 
-PyPy's choices regarding "--opt=mem". 
+PyPy's choices regarding "--opt=mem".  We 
+also want to measure builds that include
+a working set of modules and ones that include
+no modules at all (the bare minimum for an 
+interactive prompt). 
 
 XXX consider more specific target environments