Ticket #123 (closed enhancement: fixed)

Opened 12 months ago

Last modified 8 months ago

health: add input

Reported by: Nathan Weeks <weeks@…> Owned by:
Priority: minor Milestone: version 1.2
Component: health Version: version 1.1.1
Keywords: Cc:
Application Version: all Blocked By:
Blocking: Sensitive: no
Needs experiment: no
Experimental observations:

NOTE: compiled with CC_FLAGS = -m64 to ensure 8-byte long's;
verification with large.input appears to to fail when "long" is 4 bytes.

$ bin/health.gcc.serial -c -f inputs/health/large.input
Number of levels    = 4
Cities per level    = 36
Population ratio    = 10
Simulation time     = 365
Assess time         = 2
Convalescence time  = 12
Initial seed        = 23
Get sick prob.      = 0.002000
Convalescence prob. = 0.100000
Realloc prob.       = 0.150000
Sim. Variables      = expect / result
Total population    = 988000 / 988000 people
Hospitals           =  47989 /  47989 people
Personnel           =  98800 /  98800 people
Check-in's          = 704632 / 704632 people
In Villages         = 969699 / 969699 people
In Waiting List     =  11955 /  11955 people
In Assess           =   3924 /   3924 people
Inside Hospital     =   2422 /   2422 people
Average Stay        = 5.763031 / 5.763031 u/time
Program             = Health
Parameters          = inputs/health/large.input
Model               = Serial
Embedded cut-off    = none
# of Threads        = 1
Verification        = successful
Time Program        = 11.956272 seconds
Execution Date      = 2011/02/23;19:13
Execution Message   =
Architecture        = Darwin-i386;16
Load Avg [1:5:15]   = ;;
Compilation Date    = 2011/02/23;12:22
Compilation Message =
Compiler            = gcc
Compiler Flags      = -c -I../..//common -O3 -m64   -I.
Linker              = gcc
Linker Flags        = -O3 -m64  -lm

Description

When run on a modern processor (the example above used a machine with 2 x
2.93GHz quad-core Intel Xeon 5570's), the run time of the serial health
kernel with large.input is low enough (hovering around 12 seconds on
this machine) to not leave much room for scaling. It may be beneficial to have
a larger input size.

Since medium.input and large.input are identical, one solution
could be to keep medium.input as-is & make large.input larger.
Also note that tiny.input and small.input are identical; it might
be beneficial to get rid of tiny.input or modify one of them to avoid
confusion.

Change History

Changed 8 months ago by Xavier Teruel <xavier.teruel@…>

  • status changed from new to closed
  • resolution set to fixed

(In [264c87519e6edf8e7d50e8261d91649138fafde8]) Changing health's large and test inputs; large benchmark is x7 larger than medium; close #123

Note: See TracTickets for help on using tickets.