Trace number 213325

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.798878 0.838896

DiagnosticValue
CHECKS754
NODES0

General information on the benchmark

NamepseudoSeries/
aim/aim-50-1-6-2.xml
MD5SUM8605a78db337522853e73e0031deffc4
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.021996
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints130
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension130
Global constraints used (with number of constraints)

Solver Data (download as text)

0.34	   
0.34	Abscon 109 (November, 2006)
0.34	   
0.34	   configuration
0.34	     name=esac.xml
0.37	   
0.37	   instance
0.37	     name=/tmp/evaluation/213325-1168225616/unknown.xml
0.40	   
0.40	   domains being loaded...
0.41	   
0.41	   variables being loaded...
0.44	     nbVariables=100  nbDomainTypes=1  minDomainSize=2  maxDomainSize=2
0.44	       =>  wckTime=0.101  cpuTime=0.09  mem=6M951
0.44	   
0.44	   predicates being loaded...
0.44	   
0.44	   constraints being loaded...
0.55	     nbConstraints=130  nbConvertedConstraints=50  nbConvertConstraintsChecks=12  nbExtensionStructures=1
0.55	     nbSharedExtensionStructures=49  nbConflictsStructures=2  nbSharedConflictsStructures=128
0.55	     nbSharedBinaryRepresentations=2  nbEvaluationManagers=1  nbSharedEvaluationManagers=79  maxDegree=5  maxArity=3
0.55	       =>  wckTime=0.21  cpuTime=0.18  mem=7M937
0.59	   
0.59	   solver IterativeSystematicSolver being built... 
0.77	       =>  wckTime=0.431  cpuTime=0.33  mem=15M358
0.82	   
0.82	   preprocessing
0.82	     nbConstraintChecks=754  nbValidityChecks=172  nbPropagations=500  nbRevisions=778  nbUselessRevisions=570
0.82	     nbSingletonTests=203  nbEffectiveSingletonTests=0  nbESACBranches=6  nbRemovedValues=0  detectedInconsistency=no
0.82	       =>  wckTime=0.047  cpuTime=0.03  mem=15M358
0.82	   
0.82	   global
0.82	     nbConstraintChecks=754  nbValidityChecks=172  nbPropagations=500  nbRevisions=778  nbUselessRevisions=570
0.82	     nbRestartNogoods=0  solvingWckTime=0.049  solvingCpuTime=0.03  expiredTime=no  totalExploration=no
0.82	     nbFoundSolutions=1  globalCpuTime=0.41
0.82	       =>  wckTime=0.481  cpuTime=0.36  mem=15M358
0.82	   
0.82	s SATISFIABLE
0.82	v 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 0 1 1 0 0 1 0 1 0 1 0 1 1 0 0 1 0 1 0 1 1 0 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 1 0 0 1 1 0 1 0 1 0 1 0 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 
0.82	d NODES 0
0.82	d CHECKS 754
0.82	   
0.82	   totalWckTime=0.564  totalCpuTime=0.41

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/node6/watcher-213325-1168225616 -o ROOT/results/node6/solver-213325-1168225616 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/213325-1168225616/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.24 1.78 1.91 4/94 27224
/proc/meminfo: memFree=1766184/2055924 swapFree=4165672/4192956
[pid=27223] ppid=27221 vsize=18540 CPUtime=0
/proc/27223/stat : 27223 (runsolver) R 27221 27223 25677 0 -1 4194368 17 0 0 0 0 0 0 0 19 0 1 0 170957833 18984960 279 18446744073709551615 4194304 4267372 548682068944 18446744073709551615 268582841639 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/27223/statm: 4635 279 244 17 0 2626 0

[startup+0.103871 s]
/proc/loadavg: 1.24 1.78 1.91 4/94 27224
/proc/meminfo: memFree=1766184/2055924 swapFree=4165672/4192956
[pid=27223] ppid=27221 vsize=911488 CPUtime=0.06
/proc/27223/stat : 27223 (java) R 27221 27223 25677 0 -1 0 2616 0 1 0 5 1 0 0 20 0 8 0 170957833 933363712 2363 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4153795296 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/27223/statm: 227872 2363 1279 14 0 215051 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 911488

[startup+0.512919 s]
/proc/loadavg: 1.24 1.78 1.91 4/94 27224
/proc/meminfo: memFree=1766184/2055924 swapFree=4165672/4192956
[pid=27223] ppid=27221 vsize=915328 CPUtime=0.47
/proc/27223/stat : 27223 (java) R 27221 27223 25677 0 -1 0 6333 0 1 0 43 4 0 0 18 0 8 0 170957833 937295872 6072 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4155166565 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/27223/statm: 228832 6072 2154 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.838896
CPU time (s): 0.798878
CPU user time (s): 0.735888
CPU system time (s): 0.06299
CPU usage (%): 95.2297
Max. virtual memory (cumulated for all children) (KiB): 915448

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.735888
system time used= 0.06299
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8742
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= 676
involuntary context switches= 663

runsolver used 0.005999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node6 on Mon Jan  8 03:07:00 UTC 2007


IDJOB= 213325
IDBENCH= 4839
FILE ID= node6/213325-1168225616

PBS_JOBID= 3480657

Free space on /tmp= 66551 MiB

BENCH NAME= HOME/pub/bench/CPAI06/pseudoSeries/aim/aim-50-1-6-2.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/213325-1168225616/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-213325-1168225616 -o ROOT/results/node6/solver-213325-1168225616 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/213325-1168225616/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  8605a78db337522853e73e0031deffc4

RANDOM SEED= 203050988

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.240
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.240
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:      2055924 kB
MemFree:       1766664 kB
Buffers:         36284 kB
Cached:         116384 kB
SwapCached:       2916 kB
Active:         139896 kB
Inactive:        90208 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1766664 kB
SwapTotal:     4192956 kB
SwapFree:      4165672 kB
Dirty:            1732 kB
Writeback:           0 kB
Mapped:          94528 kB
Slab:            43780 kB
Committed_AS:  4961832 kB
PageTables:       2524 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= 66551 MiB



End job on node6 on Mon Jan  8 03:07:08 UTC 2007