Trace number 244488

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 0.932857 0.971321

DiagnosticValue
CHECKS573
NODES0

General information on the benchmark

Namedimacs/
jnhUnsat/jnh307_ext.xml
MD5SUM78e8763abbda076cbcafb0fe67c3a674
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.06299
SatisfiableNO
(Un)Satisfiability was proved
Number of variables100
Number of constraints897
Maximum constraint arity11
Maximum domain size2
Number of constraints which are defined in extension897
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.29	   
0.29	Abscon 109 (November, 2006)
0.29	   
0.30	   configuration
0.30	     name=esac.xml
0.33	   
0.33	   instance
0.33	     name=/tmp/evaluation/244488-1168385859/unknown.xml
0.36	   
0.36	   domains being loaded...
0.36	   
0.36	   variables being loaded...
0.39	     nbVariables=100  nbDomainTypes=1  minDomainSize=2  maxDomainSize=2
0.39	       =>  wckTime=0.096  cpuTime=0.08  mem=6M951
0.39	   
0.39	   relations being loaded...
0.44	   
0.44	   constraints being loaded...
0.61	     nbConstraints=897  nbRelationTypes=225  nbExtensionStructures=225  nbSharedExtensionStructures=672
0.61	     nbConflictsStructures=225  nbSharedConflictsStructures=672  nbSharedBinaryRepresentations=16  maxDegree=60
0.61	     maxArity=11
0.61	       =>  wckTime=0.315  cpuTime=0.22  mem=11M836
0.65	   
0.65	   solver IterativeSystematicSolver being built... 
0.87	       =>  wckTime=0.571  cpuTime=0.4  mem=23M260
0.92	   
0.92	   preprocessing
0.92	     nbConstraintChecks=573  nbValidityChecks=475  nbPropagations=238  nbRevisions=943  nbUselessRevisions=828
0.92	     nbSingletonTests=64  nbEffectiveSingletonTests=2  nbESACBranches=3  nbRemovedValues=47  detectedInconsistency=yes
0.92	       =>  wckTime=0.051  cpuTime=0.03  mem=23M260
0.92	   
0.92	   global
0.92	     nbConstraintChecks=573  nbValidityChecks=475  nbPropagations=238  nbRevisions=943  nbUselessRevisions=828
0.92	     nbRestartNogoods=0  solvingWckTime=0.052  solvingCpuTime=0.04  expiredTime=no  totalExploration=yes
0.92	     nbFoundSolutions=0  globalCpuTime=0.49
0.92	       =>  wckTime=0.625  cpuTime=0.44  mem=23M260
0.92	   
0.92	s UNSATISFIABLE
0.92	d NODES 0
0.92	d CHECKS 573
0.92	   
0.92	   totalWckTime=0.7  totalCpuTime=0.49

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/node10/watcher-244488-1168385859 -o ROOT/results/node10/solver-244488-1168385859 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/244488-1168385859/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.32 0.78 0.85 3/81 30576
/proc/meminfo: memFree=1824152/2055920 swapFree=4178216/4192956
[pid=30575] ppid=30573 vsize=906128 CPUtime=0.01
/proc/30575/stat : 30575 (java) R 30573 30575 29559 0 -1 0 1933 0 1 0 1 0 0 0 17 0 1 0 186981097 927875072 1682 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4155581175 0 4 0 7368 0 0 0 17 1 0 0
/proc/30575/statm: 226532 1683 977 14 0 214115 0

[startup+0.102638 s]
/proc/loadavg: 0.32 0.78 0.85 3/81 30576
/proc/meminfo: memFree=1824152/2055920 swapFree=4178216/4192956
[pid=30575] ppid=30573 vsize=914988 CPUtime=0.09
/proc/30575/stat : 30575 (java) R 30573 30575 29559 0 -1 0 3022 0 1 0 8 1 0 0 16 0 8 0 186981097 936947712 2768 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4072944238 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/30575/statm: 228747 2768 1435 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.510691 s]
/proc/loadavg: 0.32 0.78 0.85 3/81 30576
/proc/meminfo: memFree=1824152/2055920 swapFree=4178216/4192956
[pid=30575] ppid=30573 vsize=915328 CPUtime=0.49
/proc/30575/stat : 30575 (java) R 30573 30575 29559 0 -1 0 6398 0 1 0 45 4 0 0 16 0 8 0 186981097 937295872 6137 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4073652405 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/30575/statm: 228832 6138 2137 14 0 215302 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.971321
CPU time (s): 0.932857
CPU user time (s): 0.85387
CPU system time (s): 0.078987
CPU usage (%): 96.04
Max. virtual memory (cumulated for all children) (KiB): 915556

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.85387
system time used= 0.078987
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 10771
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= 686
involuntary context switches= 65

runsolver used 0.000999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan  9 23:37:40 UTC 2007


IDJOB= 244488
IDBENCH= 8482
FILE ID= node10/244488-1168385859

PBS_JOBID= 3522619

Free space on /tmp= 66561 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/jnhUnsat/jnh307_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/244488-1168385859/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-244488-1168385859 -o ROOT/results/node10/solver-244488-1168385859 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/244488-1168385859/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  78e8763abbda076cbcafb0fe67c3a674

RANDOM SEED= 912831334

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:       1824560 kB
Buffers:         26740 kB
Cached:         118344 kB
SwapCached:       1864 kB
Active:         122948 kB
Inactive:        56208 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1824560 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:            2000 kB
Writeback:           0 kB
Mapped:          43928 kB
Slab:            37288 kB
Committed_AS:  5567788 kB
PageTables:       2104 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= 66561 MiB



End job on node10 on Tue Jan  9 23:37:42 UTC 2007