Trace number 206865

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 ESACSAT 0.876865 0.925981

DiagnosticValue
CHECKS44035
NODES0

General information on the benchmark

NametravellingSalesman/travellingSalesman-20/
tsp-20-68_ext.xml
MD5SUMfc0652b76d1c37a99baababb747c85cb
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.857869
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables61
Number of constraints230
Maximum constraint arity3
Maximum domain size1001
Number of constraints which are defined in extension230
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.32	   
0.33	Abscon 109 (November, 2006)
0.33	   
0.33	   configuration
0.33	     name=esac.xml
0.36	   
0.36	   instance
0.36	     name=/tmp/evaluation/206865-1168179267/unknown.xml
0.40	   
0.40	   domains being loaded...
0.40	   
0.40	   variables being loaded...
0.44	     nbVariables=61  nbDomainTypes=5  minDomainSize=1  maxDomainSize=1001
0.44	       =>  wckTime=0.115  cpuTime=0.08  mem=7M931
0.44	   
0.44	   relations being loaded...
0.48	   
0.48	   constraints being loaded...
0.60	     nbConstraints=230  nbRelationTypes=23  nbSingletonDomainVariables=2  nbExtensionStructures=24
0.60	     nbSharedExtensionStructures=206  nbConflictsStructures=24  nbSharedConflictsStructures=206
0.60	     nbSharedBinaryRepresentations=20290  maxDegree=20  maxArity=3
0.60	       =>  wckTime=0.274  cpuTime=0.19  mem=11M848
0.64	   
0.64	   solver IterativeSystematicSolver being built... 
0.82	       =>  wckTime=0.49  cpuTime=0.34  mem=16M869
0.89	   
0.89	   preprocessing
0.89	     nbConstraintChecks=44035  nbValidityChecks=19697  nbPropagations=433  nbRevisions=997  nbUselessRevisions=589
0.89	     nbSingletonTests=61  nbEffectiveSingletonTests=0  nbESACBranches=1  nbRemovedValues=21769  detectedInconsistency=no
0.89	       =>  wckTime=0.07  cpuTime=0.03  mem=16M869
0.89	   
0.89	   global
0.89	     nbConstraintChecks=44035  nbValidityChecks=19697  nbPropagations=433  nbRevisions=997  nbUselessRevisions=589
0.89	     nbRestartNogoods=0  solvingWckTime=0.072  solvingCpuTime=0.04  expiredTime=no  totalExploration=no
0.89	     nbFoundSolutions=1  globalCpuTime=0.44
0.89	       =>  wckTime=0.566  cpuTime=0.38  mem=16M869
0.90	   
0.90	s SATISFIABLE
0.90	v 18 5 10 4 19 2 15 3 6 6 14 3 12 2 1 13 11 9 20 10 5 16 9 3 16 0 2 7 13 9 3 6 4 5 7 0 8 0 17 0 9 11 14 20 23 25 38 47 57 73 76 76 83 92 98 103 103 103 103 103 0 
0.90	d NODES 0
0.90	d CHECKS 44035
0.90	   
0.90	   totalWckTime=0.65  totalCpuTime=0.44

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/node56/watcher-206865-1168179267 -o ROOT/results/node56/solver-206865-1168179267 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/206865-1168179267/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: 1.92 1.98 1.98 4/81 6619
/proc/meminfo: memFree=1518880/2055920 swapFree=4184772/4192956
[pid=6618] ppid=6616 vsize=18540 CPUtime=0
/proc/6618/stat : 6618 (runsolver) R 6616 6618 5158 0 -1 4194368 17 0 0 0 0 0 0 0 18 0 1 0 166324862 18984960 279 18446744073709551615 4194304 4267372 548682068960 18446744073709551615 253307186471 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/6618/statm: 4635 279 244 17 0 2626 0

[startup+0.107657 s]
/proc/loadavg: 1.92 1.98 1.98 4/81 6619
/proc/meminfo: memFree=1518880/2055920 swapFree=4184772/4192956
[pid=6618] ppid=6616 vsize=913228 CPUtime=0.08
/proc/6618/stat : 6618 (java) D 6616 6618 5158 0 -1 0 2919 0 1 0 6 2 0 0 19 0 8 0 166324862 935145472 2665 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 2147483391 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/6618/statm: 228307 2665 1396 14 0 215208 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 913228

[startup+0.515697 s]
/proc/loadavg: 1.92 1.98 1.98 4/81 6619
/proc/meminfo: memFree=1518880/2055920 swapFree=4184772/4192956
[pid=6618] ppid=6616 vsize=915328 CPUtime=0.47
/proc/6618/stat : 6618 (java) R 6616 6618 5158 0 -1 0 6565 0 1 0 43 4 0 0 18 0 8 0 166324862 937295872 6304 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4072897127 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/6618/statm: 228832 6304 2138 14 0 215302 0
Current children cumulated CPU time (s) 0.47
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.925981
CPU time (s): 0.876865
CPU user time (s): 0.802877
CPU system time (s): 0.073988
CPU usage (%): 94.6958
Max. virtual memory (cumulated for all children) (KiB): 915444

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.802877
system time used= 0.073988
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9244
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= 935
involuntary context switches= 943

runsolver used 0.006998 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node56 on Sun Jan  7 14:14:27 UTC 2007


IDJOB= 206865
IDBENCH= 4241
FILE ID= node56/206865-1168179267

PBS_JOBID= 3479081

Free space on /tmp= 66550 MiB

BENCH NAME= HOME/pub/bench/CPAI06/travellingSalesman/travellingSalesman-20/tsp-20-68_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/206865-1168179267/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node56/watcher-206865-1168179267 -o ROOT/results/node56/solver-206865-1168179267 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/206865-1168179267/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  fc0652b76d1c37a99baababb747c85cb

RANDOM SEED= 489527122

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.232
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.232
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:       1519296 kB
Buffers:         37908 kB
Cached:         352008 kB
SwapCached:       2104 kB
Active:         154588 kB
Inactive:       312500 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1519296 kB
SwapTotal:     4192956 kB
SwapFree:      4184772 kB
Dirty:            1792 kB
Writeback:           0 kB
Mapped:          91624 kB
Slab:            54504 kB
Committed_AS:  3269036 kB
PageTables:       2064 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= 66550 MiB



End job on node56 on Sun Jan  7 14:14:28 UTC 2007