Trace number 191568

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.908861 0.981583

DiagnosticValue
CHECKS2803
NODES0

General information on the benchmark

Namecomposed/composed-75-1-80/
composed-75-1-80-4_ext.xml
MD5SUMd9245102b14af27eab4c58b2c9346eb1
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.05999
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables83
Number of constraints702
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension702
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.31	   
0.31	Abscon 109 (November, 2006)
0.31	   
0.31	   configuration
0.31	     name=esac.xml
0.35	   
0.35	   instance
0.35	     name=/tmp/evaluation/191568-1168095869/unknown.xml
0.38	   
0.38	   domains being loaded...
0.38	   
0.38	   variables being loaded...
0.42	     nbVariables=83  nbDomainTypes=1  minDomainSize=10  maxDomainSize=10
0.42	       =>  wckTime=0.108  cpuTime=0.09  mem=6M951
0.42	   
0.42	   relations being loaded...
0.52	   
0.52	   constraints being loaded...
0.68	     nbConstraints=702  nbRelationTypes=702  nbExtensionStructures=702  nbSharedExtensionStructures=0
0.68	     nbConflictsStructures=702  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=13360  maxDegree=28
0.68	     maxArity=2
0.68	       =>  wckTime=0.365  cpuTime=0.25  mem=12M803
0.72	   
0.73	   solver IterativeSystematicSolver being built... 
0.89	       =>  wckTime=0.57  cpuTime=0.38  mem=15M56
0.91	   
0.91	   preprocessing
0.91	     nbConstraintChecks=2803  nbPropagations=128  nbRevisions=382  nbUselessRevisions=258  nbSingletonTests=4
0.91	     nbEffectiveSingletonTests=4  nbESACBranches=0  nbRemovedValues=84  detectedInconsistency=yes
0.91	       =>  wckTime=0.024  cpuTime=0.01  mem=15M56
0.91	   
0.91	   global
0.92	     nbConstraintChecks=2803  nbPropagations=128  nbRevisions=382  nbUselessRevisions=258  nbRestartNogoods=0
0.92	     solvingWckTime=0.026  solvingCpuTime=0.01  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
0.92	     globalCpuTime=0.44
0.92	       =>  wckTime=0.599  cpuTime=0.39  mem=15M56
0.92	   
0.92	s UNSATISFIABLE
0.92	d NODES 0
0.92	d CHECKS 2803
0.92	   
0.92	   totalWckTime=0.679  totalCpuTime=0.45

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/node25/watcher-191568-1168095869 -o ROOT/results/node25/solver-191568-1168095869 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/191568-1168095869/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.74 1.42 1.62 3/83 2899
/proc/meminfo: memFree=1626144/2055920 swapFree=4192812/4192956
[pid=2898] ppid=2895 vsize=1784 CPUtime=0
/proc/2898/stat : 2898 (java) D 2895 2898 2753 0 -1 0 165 0 0 0 0 0 0 0 18 0 1 0 157979604 1826816 136 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 4294960144 0 2147483391 4096 0 18446744072099781622 0 0 17 0 0 0
/proc/2898/statm: 446 136 102 14 0 91 0

[startup+0.107746 s]
/proc/loadavg: 0.74 1.42 1.62 3/83 2899
/proc/meminfo: memFree=1626144/2055920 swapFree=4192812/4192956
[pid=2898] ppid=2895 vsize=914988 CPUtime=0.08
/proc/2898/stat : 2898 (java) R 2895 2898 2753 0 -1 0 2988 0 1 0 7 1 0 0 17 0 8 0 157979604 936947712 2734 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 2147483391 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/2898/statm: 228747 2734 1426 14 0 215242 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 914988

[startup+0.516814 s]
/proc/loadavg: 0.74 1.42 1.62 3/83 2899
/proc/meminfo: memFree=1626144/2055920 swapFree=4192812/4192956
[pid=2898] ppid=2895 vsize=915328 CPUtime=0.49
/proc/2898/stat : 2898 (java) R 2895 2898 2753 0 -1 0 6401 0 1 0 46 3 0 0 18 0 8 0 157979604 937295872 6140 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/2898/statm: 228832 6140 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.981583
CPU time (s): 0.908861
CPU user time (s): 0.843871
CPU system time (s): 0.06499
CPU usage (%): 92.5914
Max. virtual memory (cumulated for all children) (KiB): 915564

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.843871
system time used= 0.06499
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8741
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= 902
involuntary context switches= 759

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node25 on Sat Jan  6 15:04:30 UTC 2007


IDJOB= 191568
IDBENCH= 3060
FILE ID= node25/191568-1168095869

PBS_JOBID= 3476724

Free space on /tmp= 66549 MiB

BENCH NAME= HOME/pub/bench/CPAI06/composed/composed-75-1-80/composed-75-1-80-4_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/191568-1168095869/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node25/watcher-191568-1168095869 -o ROOT/results/node25/solver-191568-1168095869 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/191568-1168095869/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  d9245102b14af27eab4c58b2c9346eb1

RANDOM SEED= 327318039

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.279
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.279
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:       1627104 kB
Buffers:         46584 kB
Cached:         262408 kB
SwapCached:          0 kB
Active:          97188 kB
Inactive:       260276 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1627104 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2328 kB
Writeback:           0 kB
Mapped:          67504 kB
Slab:            56332 kB
Committed_AS:  2926656 kB
PageTables:       2180 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= 66549 MiB



End job on node25 on Sat Jan  6 15:04:33 UTC 2007