Trace number 2070750

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock time.

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
Choco2.1.1 2009-06-10SAT 0.945855 0.966782

DiagnosticValue
CHECKS0
NODES162

General information on the benchmark

Namecsp/primes-20/
normalized-primes-20-20-3-1.xml
MD5SUM9d7c5b819f44e9796c93b064d36b2c7e
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.019996
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints20
Maximum constraint arity4
Maximum domain size70
Number of constraints which are defined in extension0
Number of constraints which are defined in intension20
Global constraints used (with number of constraints)

Solver Data 

0.88/0.95	s SATISFIABLE
0.88/0.95	v 64 18 45 60 57 52 68 3 18 7 58 2 48 42 8 16 24 2 28 12 48 33 11 51 22 44 2 23 10 53 36 64 18 53 55 20 51 16 60 59 18 29 15 60 19 43 46 10 49 25 10 68 27 4 18 63 15 57 51 22 61 11 67 42 42 7 71 54 30 52 53 55 9 26 9 50 48 7 8 14 49 53 30 57 21 40 14 38 36 57 35 57 62 33 55 70 49 56 49 61 
0.88/0.95	d AC 32
0.88/0.95	d RUNTIME 0.835
0.88/0.95	d NODES 162
0.88/0.95	d NODES/s 194
0.88/0.95	d BACKTRACKS 115
0.88/0.95	d BACKTRACKS/s 138
0.88/0.95	d CHECKS 0
0.88/0.95	d CHECKS/s 0
0.88/0.95	c SAT 0.835 TIME      162 NDS    255 PARSTIME      287 BUILDPB       293 RES       true RESTART       1 HEURISTIC       true RANDVAL

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2070750-1247351702/watcher-2070750-1247351702 -o /tmp/evaluation-result-2070750-1247351702/solver-2070750-1247351702 -C 1800 -W 2000 -M 900 java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2070750-1247351702.xml -h 1 -randval true -ac 32 -rest true -rb 10 -rg 1.3 -saclim 60 -s true -verb 0 -seed 11041979 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.28 2.28 2.16 4/81 16373
/proc/meminfo: memFree=1855688/2055920 swapFree=4192812/4192956
[pid=16373] ppid=16371 vsize=18576 CPUtime=0
/proc/16373/stat : 16373 (runsolver) R 16371 16373 16336 0 -1 4194368 16 0 0 0 0 0 0 0 19 0 1 0 22236558 19021824 284 996147200 4194304 4302564 548682068192 18446744073709551615 253307186471 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/16373/statm: 4644 284 249 26 0 2626 0

[startup+0.0320869 s]
/proc/loadavg: 2.28 2.28 2.16 4/81 16373
/proc/meminfo: memFree=1855688/2055920 swapFree=4192812/4192956
[pid=16373] ppid=16371 vsize=859244 CPUtime=0.01
/proc/16373/stat : 16373 (java) S 16371 16373 16336 0 -1 0 1711 0 1 0 1 0 0 0 18 0 3 0 22236558 879865856 1390 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16784584 18446744073709551615 0 0 17 1 0 0
/proc/16373/statm: 214811 1390 570 9 0 209726 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 859244

[startup+0.101007 s]
/proc/loadavg: 2.28 2.28 2.16 4/81 16373
/proc/meminfo: memFree=1855688/2055920 swapFree=4192812/4192956
[pid=16373] ppid=16371 vsize=864064 CPUtime=0.08
/proc/16373/stat : 16373 (java) S 16371 16373 16336 0 -1 0 3687 0 1 0 6 2 0 0 18 0 9 0 22236558 884801536 3152 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/16373/statm: 216016 3152 1640 9 0 210484 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 864064

[startup+0.301025 s]
/proc/loadavg: 2.28 2.28 2.16 4/81 16373
/proc/meminfo: memFree=1855688/2055920 swapFree=4192812/4192956
[pid=16373] ppid=16371 vsize=864188 CPUtime=0.28
/proc/16373/stat : 16373 (java) S 16371 16373 16336 0 -1 0 4796 0 1 0 26 2 0 0 18 0 9 0 22236558 884928512 4212 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/16373/statm: 216047 4212 1880 9 0 210515 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 864188

[startup+0.70106 s]
/proc/loadavg: 2.28 2.28 2.16 4/81 16373
/proc/meminfo: memFree=1855688/2055920 swapFree=4192812/4192956
[pid=16373] ppid=16371 vsize=864556 CPUtime=0.68
/proc/16373/stat : 16373 (java) S 16371 16373 16336 0 -1 0 6888 0 1 0 64 4 0 0 18 0 9 0 22236558 885305344 6269 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/16373/statm: 216139 6269 1961 9 0 210607 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 864556

Solver just ended. Dumping a history of the last processes samples

[startup+0.901075 s]
/proc/loadavg: 2.28 2.28 2.16 4/81 16373
/proc/meminfo: memFree=1855688/2055920 swapFree=4192812/4192956
[pid=16373] ppid=16371 vsize=864556 CPUtime=0.88
/proc/16373/stat : 16373 (java) S 16371 16373 16336 0 -1 0 7238 0 1 0 83 5 0 0 18 0 9 0 22236558 885305344 6619 996147200 134512640 134550932 4294955840 18446744073709551615 4294960144 0 0 0 16800975 18446744073709551615 0 0 17 1 0 0
/proc/16373/statm: 216139 6619 1961 9 0 210607 0
Current children cumulated CPU time (s) 0.88
Current children cumulated vsize (KiB) 864556

Child status: 0
Real time (s): 0.966782
CPU time (s): 0.945855
CPU user time (s): 0.884865
CPU system time (s): 0.06099
CPU usage (%): 97.8354
Max. virtual memory (cumulated for all children) (KiB): 864556

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.884865
system time used= 0.06099
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 7461
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 586
involuntary context switches= 519

runsolver used 0.001999 second user time and 0.012998 second system time

The end

Launcher Data 

Begin job on node25 at 2009-07-12 00:35:02
IDJOB=2070750
IDBENCH=55392
IDSOLVER=737
FILE ID=node25/2070750-1247351702
PBS_JOBID= 9506963
Free space on /tmp= 66300 MiB

SOLVER NAME= Choco2.1.1 2009-06-10
BENCH NAME= CPAI08/csp/primes-20/normalized-primes-20-20-3-1.xml
COMMAND LINE= java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file BENCHNAME -h 1 -randval true -ac 32 -rest true -rb 10 -rg 1.3 -saclim 60 -s true -verb 0 -seed 11041979
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2070750-1247351702/watcher-2070750-1247351702 -o /tmp/evaluation-result-2070750-1247351702/solver-2070750-1247351702 -C 1800 -W 2000 -M 900  java -Xms700M -Xmx700M -jar HOME/choco-2.1.1.jar -file HOME/instance-2070750-1247351702.xml -h 1 -randval true -ac 32 -rest true -rb 10 -rg 1.3 -saclim 60 -s true -verb 0 -seed 11041979

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 9d7c5b819f44e9796c93b064d36b2c7e
RANDOM SEED=2026226980

node25.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.231
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.231
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1856232 kB
Buffers:         20052 kB
Cached:          92352 kB
SwapCached:          0 kB
Active:         114568 kB
Inactive:        36972 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1856232 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2800 kB
Writeback:           0 kB
Mapped:          59520 kB
Slab:            33324 kB
Committed_AS:   201276 kB
PageTables:       1984 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66296 MiB
End job on node25 at 2009-07-12 00:35:03