Scenario 136

Creator Jon Fox
When 14 Jan 2015
Description 7.4.36 not properly restricting number of wu based on app_config.xml for Collatz (Solo_Collatz)
Input files client_state.xml
global_prefs.xml
global_prefs_override.xml
cc_config.xml
Do new simulation

Simulations

ID
Click for details
Who When Parameters Results Comments
1 Jon Fox 20 Jan 2015
Existing jobs only: no
Round-robin only: no
scheduler EDF sim: no
Include empty projects: no
REC half-life: 864000.000000
Simulation duration: 86400.000000
Time step: 60.000000

        
wasted fraction 0.000000
Idle fraction 0.000000
Share violation 0.000000
Monotony 0.602596
RPCs per job 0.295455

        
By Jon Fox (20 Jan 2015):
BM appears to be continuing to ignore the app_config settings -- app_config for einstein: 0.20 0.25 4 einsteinbinary_BRP4G 0.20 0.25 4 einsteinbinary_BRP5 app_config for collatz: 1.00 0.75 4 solo_collatz 1.00 0.75 4 mini_collatz 1.00 1.00 4 large_collatz
0 Jon Fox 14 Jan 2015
Existing jobs only: no
Round-robin only: no
scheduler EDF sim: no
Include empty projects: no
REC half-life: 864000.000000
Simulation duration: 86400.000000
Time step: 60.000000

        
wasted fraction 0.000000
Idle fraction 0.000000
Share violation 0.000000
Monotony 0.602596
RPCs per job 0.295455

        
By Jon Fox (14 Jan 2015):
attempting to constrain number of cpu jobs to three (3) to allocate a full cpu for collatz gpu wu. prior to 7.4.36 this was effective via the cpu and gpu usage tags set at cpu 1.0 and gpu 0.75.

Copyright © 2017 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.