Trace number 220817

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 ESACUNSAT 1.06884 1.07467

DiagnosticValue
CHECKS51947
NODES0

General information on the benchmark

Nameehi/ehi-90/
ehi-90-315-46_ext.xml
MD5SUM42b5a69e38ed270db694baf473f43393
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.228965
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables315
Number of constraints4358
Maximum constraint arity2
Maximum domain size7
Number of constraints which are defined in extension4358
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.30	   
0.30	Abscon 109 (November, 2006)
0.30	   
0.30	   configuration
0.30	     name=esac.xml
0.33	   
0.33	   instance
0.33	     name=/tmp/evaluation/220817-1168256230/unknown.xml
0.36	   
0.36	   domains being loaded...
0.36	   
0.36	   variables being loaded...
0.43	     nbVariables=315  nbDomainTypes=1  minDomainSize=7  maxDomainSize=7
0.43	       =>  wckTime=0.134  cpuTime=0.11  mem=7M927
0.43	   
0.43	   relations being loaded...
0.46	   
0.46	   constraints being loaded...
0.75	     nbConstraints=4358  nbRelationTypes=83  nbExtensionStructures=83  nbSharedExtensionStructures=4275
0.75	     nbConflictsStructures=83  nbSharedConflictsStructures=4275  nbSharedBinaryRepresentations=1144  maxDegree=30
0.75	     maxArity=2
0.75	       =>  wckTime=0.45  cpuTime=0.33  mem=20M614
0.81	   
0.81	   solver IterativeSystematicSolver being built... 
0.99	       =>  wckTime=0.688  cpuTime=0.48  mem=17M831
1.05	   
1.05	   preprocessing
1.05	     nbConstraintChecks=51947  nbPropagations=789  nbRevisions=12008  nbUselessRevisions=11158  nbSingletonTests=45
1.05	     nbEffectiveSingletonTests=5  nbESACBranches=3  nbRemovedValues=185  detectedInconsistency=yes
1.05	       =>  wckTime=0.063  cpuTime=0.04  mem=17M831
1.05	   
1.05	   global
1.05	     nbConstraintChecks=51947  nbPropagations=789  nbRevisions=12008  nbUselessRevisions=11158  nbRestartNogoods=0
1.05	     solvingWckTime=0.066  solvingCpuTime=0.05  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
1.05	     globalCpuTime=0.59
1.05	       =>  wckTime=0.755  cpuTime=0.53  mem=17M831
1.06	   
1.06	s UNSATISFIABLE
1.06	d NODES 0
1.06	d CHECKS 51947
1.06	   
1.06	   totalWckTime=0.831  totalCpuTime=0.59

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node60/watcher-220817-1168256230 -o ROOT/results/node60/solver-220817-1168256230 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/220817-1168256230/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.20 0.19 0.67 2/68 2004
/proc/meminfo: memFree=1761952/2055920 swapFree=4192812/4192956
[pid=2003] ppid=2000 vsize=220 CPUtime=0
/proc/2003/stat : 2003 (java) R 2000 2003 1636 0 -1 0 47 0 0 0 0 0 0 0 19 0 1 0 174021808 225280 31 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 5536397 0 0 4096 0 0 0 0 17 1 0 0
/proc/2003/statm: 73 35 27 14 0 5 0

[startup+0.102717 s]
/proc/loadavg: 0.20 0.19 0.67 2/68 2004
/proc/meminfo: memFree=1761952/2055920 swapFree=4192812/4192956
[pid=2003] ppid=2000 vsize=914988 CPUtime=0.08
/proc/2003/stat : 2003 (java) R 2000 2003 1636 0 -1 0 2996 0 1 0 7 1 0 0 22 0 8 0 174021808 936947712 2742 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4072926602 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/2003/statm: 228747 2742 1427 14 0 215242 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 914988

[startup+0.510755 s]
/proc/loadavg: 0.20 0.19 0.67 2/68 2004
/proc/meminfo: memFree=1761952/2055920 swapFree=4192812/4192956
[pid=2003] ppid=2000 vsize=915328 CPUtime=0.49
/proc/2003/stat : 2003 (java) R 2000 2003 1636 0 -1 0 6494 0 1 0 46 3 0 0 16 0 8 0 174021808 937295872 6233 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4152819938 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/2003/statm: 228832 6233 2138 14 0 215302 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 1.07467
CPU time (s): 1.06884
CPU user time (s): 0.995848
CPU system time (s): 0.072988
CPU usage (%): 99.4574
Max. virtual memory (cumulated for all children) (KiB): 915588

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.995848
system time used= 0.072988
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 10758
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= 802
involuntary context switches= 102

runsolver used 0.002999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node60 on Mon Jan  8 11:37:14 UTC 2007


IDJOB= 220817
IDBENCH= 5380
FILE ID= node60/220817-1168256230

PBS_JOBID= 3482571

Free space on /tmp= 66563 MiB

BENCH NAME= HOME/pub/bench/CPAI06/ehi/ehi-90/ehi-90-315-46_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/220817-1168256230/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node60/watcher-220817-1168256230 -o ROOT/results/node60/solver-220817-1168256230 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/220817-1168256230/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  42b5a69e38ed270db694baf473f43393

RANDOM SEED= 56518869

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.236
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.236
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:       1762544 kB
Buffers:         49344 kB
Cached:         167848 kB
SwapCached:          0 kB
Active:         133664 kB
Inactive:       103716 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1762544 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2044 kB
Writeback:           0 kB
Mapped:          30408 kB
Slab:            41728 kB
Committed_AS:  4126164 kB
PageTables:       1684 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= 66563 MiB



End job on node60 on Mon Jan  8 11:37:27 UTC 2007