User Tools

Site Tools


documentation:performance

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
documentation:performance [19:58 26.11.2013] Walterdocumentation:performance [20:25 18.02.2014] (current) – [Hardware] Walter
Line 1: Line 1:
-~~NOTOC~~ 
- 
 ===== Performance and scalability ===== ===== Performance and scalability =====
  
Line 14: Line 12:
   * **Memory usage** in terms of the physical memory (RAM) used by the simulation, using the resident set size (RSS) from the ''/proc/self/stat'' pseudo-file.   * **Memory usage** in terms of the physical memory (RAM) used by the simulation, using the resident set size (RSS) from the ''/proc/self/stat'' pseudo-file.
  
-==== Scaling with problem size ====+==== Scalability with problem size ====
  
 We investigated the scalability with respect to problem size to see how performance in terms of the execution time and memory usage (RAM) scales with increasing population size or lattice size. We investigated the scalability with respect to problem size to see how performance in terms of the execution time and memory usage (RAM) scales with increasing population size or lattice size.
Line 48: Line 46:
 ==== Hardware ==== ==== Hardware ====
  
-All simulations were performed on a [[http://ark.intel.com/products/41316|Intel Core i7-860 vPro]]. +All simulations were performed on a [[http://ark.intel.com/products/41316|Intel Core i7-860 vPro]]. ++++Hardware specification |
-++++ Hardware specification |+
 | # of Cores | 4 | | # of Cores | 4 |
 | # of Threads | 8 (hyperthreading) | | # of Threads | 8 (hyperthreading) |
Line 60: Line 57:
 ===== Results ===== ===== Results =====
  
 +==== Benchmark tests ====
 ^ ODE |  {{:documentation:performance:ode_25.png?link&125| }} | {{:documentation:performance:ode_100.png?link&125| }} | {{:documentation:performance:ode_400.png?link&125| }} | {{:documentation:performance:ode_2500.png?link&125| }} | {{:documentation:performance:ode_10000.png?link&125| }} | {{:documentation:performance:ode_40000.png?link&125| }} | ^ ODE |  {{:documentation:performance:ode_25.png?link&125| }} | {{:documentation:performance:ode_100.png?link&125| }} | {{:documentation:performance:ode_400.png?link&125| }} | {{:documentation:performance:ode_2500.png?link&125| }} | {{:documentation:performance:ode_10000.png?link&125| }} | {{:documentation:performance:ode_40000.png?link&125| }} |
 | Cells | 25 | 100 | 400 | 2500 | 10000 | 40000 | | Cells | 25 | 100 | 400 | 2500 | 10000 | 40000 |
Line 70: Line 68:
 | Cells | 8 | 50 | 200 | 800 | 5000 | | Cells | 8 | 50 | 200 | 800 | 5000 |
  
 +-----
 +==== Performance statistics ====
  
 ^ ^ Problem size \\ (absolute) ^ Problem size \\ (relative) ^ ^ Multi-threading ^ ^ ^ Problem size \\ (absolute) ^ Problem size \\ (relative) ^ ^ Multi-threading ^
Line 77: Line 77:
 ^ CPM \\ {{:documentation:performance:cpm_2000.png?link&100| }}| {{:documentation:performance:performance_cpm_problemsize_absolute.png?direct&300|}} ((Execution time is almost linearly with number of ''CPM'' cells. Small memory footprint, despite ''edgelist'' tracking.)) | {{:documentation:performance:performance_cpm_problemsize_relative.png?direct&300|}} ((Exec. time per ''CPM'' cell is almost constant, although performance decreases for larger systems. Decrease of memory usage per cell is here mostly due to use of large lattice in all cases.)) | | {{:documentation:performance:performance_cpm_multithreading.png?direct&300|}} ((Parallel processing is not available for ''CPM'' simulations. Therefore, multithreading does not results in speed-up. Instead, the multithreading overhead even slightly decreases performance.)) | ^ CPM \\ {{:documentation:performance:cpm_2000.png?link&100| }}| {{:documentation:performance:performance_cpm_problemsize_absolute.png?direct&300|}} ((Execution time is almost linearly with number of ''CPM'' cells. Small memory footprint, despite ''edgelist'' tracking.)) | {{:documentation:performance:performance_cpm_problemsize_relative.png?direct&300|}} ((Exec. time per ''CPM'' cell is almost constant, although performance decreases for larger systems. Decrease of memory usage per cell is here mostly due to use of large lattice in all cases.)) | | {{:documentation:performance:performance_cpm_multithreading.png?direct&300|}} ((Parallel processing is not available for ''CPM'' simulations. Therefore, multithreading does not results in speed-up. Instead, the multithreading overhead even slightly decreases performance.)) |
 ^ CPM + PDE \\ {{:documentation:performance:cpmpde_400.png?link&125| }} | {{:documentation:performance:performance_cpmpde_problemsize_absolute.png?direct&300|}} | {{:documentation:performance:performance_cpmpde_problemsize_relative.png?direct&300|}} | |{{:documentation:performance:performance_cpmpde_multithreading.png?direct&300|}} | ^ CPM + PDE \\ {{:documentation:performance:cpmpde_400.png?link&125| }} | {{:documentation:performance:performance_cpmpde_problemsize_absolute.png?direct&300|}} | {{:documentation:performance:performance_cpmpde_problemsize_relative.png?direct&300|}} | |{{:documentation:performance:performance_cpmpde_multithreading.png?direct&300|}} |
 +
documentation/performance.1385492321.txt.gz · Last modified: 19:58 26.11.2013 by Walter

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki