Trace number 242940

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, and are wall clock time (not CPU 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
Abscon 109 ACSAT 0.744885 0.84871

DiagnosticValue
CHECKS731
NODES52

General information on the benchmark

Namedimacs/aim-50/
aim-50-6-0-sat-2_ext.xml
MD5SUMcca28c2173d29303fa9720314f4af229
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.024995
SatisfiableYES
(Un)Satisfiability was proved
Number of variables50
Number of constraints284
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension284
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.33	   
0.33	Abscon 109 (November, 2006)
0.33	   
0.33	   configuration
0.33	     name=mac.xml
0.36	   
0.36	   instance
0.36	     name=/tmp/evaluation/242940-1168085588/unknown.xml
0.39	   
0.39	   domains being loaded...
0.40	   
0.40	   variables being loaded...
0.42	     nbVariables=50  nbDomainTypes=1  minDomainSize=2  maxDomainSize=2
0.42	       =>  wckTime=0.087  cpuTime=0.08  mem=6M951
0.42	   
0.42	   relations being loaded...
0.43	   
0.43	   constraints being loaded...
0.53	     nbConstraints=284  nbRelationTypes=19  nbExtensionStructures=19  nbSharedExtensionStructures=265
0.53	     nbConflictsStructures=19  nbSharedConflictsStructures=265  nbSharedBinaryRepresentations=9  maxDegree=18
0.53	     maxArity=3
0.53	       =>  wckTime=0.193  cpuTime=0.15  mem=7M959
0.56	   
0.56	   solver IterativeSystematicSolver being built... 
0.73	       =>  wckTime=0.401  cpuTime=0.3  mem=16M404
0.74	   
0.74	   preprocessing
0.74	     nbConstraintChecks=0  nbPropagations=50  nbRevisions=0  nbUselessRevisions=0  nbRemovedValues=0
0.74	     detectedInconsistency=no
0.74	       =>  wckTime=0.0080  cpuTime=0.0  mem=16M404
0.78	   
0.78	   search
0.78	     run=0  nbConstraintChecks=731  nbValidityChecks=194  nbPropagations=115  nbRevisions=813  nbUselessRevisions=740
0.78	     nbAssignments=52  nbFailedAssignments=2  nbBacktracks=0  nbVisitedNodes=55  nbRestartNogoods=0  mapSize=0
0.78	     nbInferences=0  nbTooLargeKeys=0
0.78	       =>  wckTime=0.045  cpuTime=0.02  mem=16M404
0.78	   
0.78	   global
0.78	     nbConstraintChecks=731  nbValidityChecks=194  nbPropagations=165  nbRevisions=813  nbUselessRevisions=740
0.78	     nbRestartNogoods=0  solvingWckTime=0.047  solvingCpuTime=0.02  expiredTime=no  totalExploration=no
0.78	     nbFoundSolutions=1  globalCpuTime=0.37
0.78	       =>  wckTime=0.45  cpuTime=0.32  mem=16M404
0.79	   
0.79	s SATISFIABLE
0.79	v 0 0 1 0 1 1 0 1 0 0 0 0 1 0 0 0 0 1 0 0 1 1 0 0 1 1 0 1 0 0 0 1 1 1 1 0 1 1 0 1 0 1 0 0 1 0 1 0 0 1 
0.79	d NODES 52
0.79	d CHECKS 731
0.79	   
0.79	   totalWckTime=0.526  totalCpuTime=0.38

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node19/watcher-242940-1168085588 -o ROOT/results/node19/solver-242940-1168085588 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/242940-1168085588/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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

/proc/loadavg: 0.06 0.59 1.27 1/81 26457
/proc/meminfo: memFree=1238696/2055920 swapFree=4171232/4192956
[pid=26456] ppid=26454 vsize=1784 CPUtime=0
/proc/26456/stat : 26456 (java) D 26454 26456 26066 0 -1 0 165 0 0 0 0 0 0 0 19 0 1 0 156954864 1826816 136 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 4294960144 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/26456/statm: 446 136 102 14 0 91 0

[startup+0.102777 s]
/proc/loadavg: 0.06 0.59 1.27 1/81 26457
/proc/meminfo: memFree=1238696/2055920 swapFree=4171232/4192956
[pid=26456] ppid=26454 vsize=907808 CPUtime=0.05
/proc/26456/stat : 26456 (java) R 26454 26456 26066 0 -1 0 2499 0 1 0 4 1 0 0 19 0 4 0 156954864 929595392 2246 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4153615878 0 4 0 23755 18446744073709551615 0 0 17 0 0 0
/proc/26456/statm: 226952 2246 1230 14 0 214535 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 907808

[startup+0.51085 s]
/proc/loadavg: 0.06 0.59 1.27 1/81 26457
/proc/meminfo: memFree=1238696/2055920 swapFree=4171232/4192956
[pid=26456] ppid=26454 vsize=915328 CPUtime=0.46
/proc/26456/stat : 26456 (java) S 26454 26456 26066 0 -1 0 6413 0 1 0 43 3 0 0 16 0 8 0 156954864 937295872 6152 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/26456/statm: 228832 6152 2147 14 0 215302 0
Current children cumulated CPU time (s) 0.46
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.84871
CPU time (s): 0.744885
CPU user time (s): 0.690894
CPU system time (s): 0.053991
CPU usage (%): 87.7667
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.690894
system time used= 0.053991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9000
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= 127

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node19 on Sat Jan  6 12:13:15 UTC 2007


IDJOB= 242940
IDBENCH= 7430
FILE ID= node19/242940-1168085588

PBS_JOBID= 3476306

Free space on /tmp= 66312 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/aim-50/aim-50-6-0-sat-2_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/242940-1168085588/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node19/watcher-242940-1168085588 -o ROOT/results/node19/solver-242940-1168085588 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/242940-1168085588/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  cca28c2173d29303fa9720314f4af229

RANDOM SEED= 599842624

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.260
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.260
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:       1239248 kB
Buffers:         70156 kB
Cached:         610824 kB
SwapCached:      10036 kB
Active:         284240 kB
Inactive:       432036 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1239248 kB
SwapTotal:     4192956 kB
SwapFree:      4171232 kB
Dirty:            1764 kB
Writeback:           0 kB
Mapped:          44608 kB
Slab:            85396 kB
Committed_AS:  3666612 kB
PageTables:       2208 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= 66312 MiB



End job on node19 on Sat Jan  6 12:13:32 UTC 2007