Trace number 227333

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 1.00585 1.04242

DiagnosticValue
CHECKS30607
NODES44

General information on the benchmark

Nametightness/tightness0.1/
rand-2-40-8-753-100-5_ext.xml
MD5SUM789bb21c78bc2729112e91a1dfccd5a4
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.325949
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints753
Maximum constraint arity2
Maximum domain size8
Number of constraints which are defined in extension753
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.32	   
0.32	Abscon 109 (November, 2006)
0.32	   
0.32	   configuration
0.32	     name=esac.xml
0.35	   
0.35	   instance
0.35	     name=/tmp/evaluation/227333-1168277923/unknown.xml
0.38	   
0.38	   domains being loaded...
0.39	   
0.39	   variables being loaded...
0.42	     nbVariables=40  nbDomainTypes=1  minDomainSize=8  maxDomainSize=8
0.42	       =>  wckTime=0.103  cpuTime=0.09  mem=6M951
0.42	   
0.42	   relations being loaded...
0.52	   
0.52	   constraints being loaded...
0.71	     nbConstraints=752  nbRelationTypes=753  nbExtensionStructures=752  nbSharedExtensionStructures=0
0.71	     nbConflictsStructures=752  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=11899  maxDegree=39
0.71	     maxArity=2
0.71	       =>  wckTime=0.388  cpuTime=0.26  mem=11M848
0.75	   
0.75	   solver IterativeSystematicSolver being built... 
0.92	       =>  wckTime=0.606  cpuTime=0.39  mem=15M6
0.98	   
0.98	   preprocessing
0.98	     nbConstraintChecks=22134  nbPropagations=865  nbRevisions=4902  nbUselessRevisions=3882  nbSingletonTests=49
0.98	     nbEffectiveSingletonTests=0  nbESACBranches=6  nbRemovedValues=0  detectedInconsistency=no
0.98	       =>  wckTime=0.056  cpuTime=0.04  mem=15M6
1.01	   
1.01	   search
1.01	     run=0  nbConstraintChecks=8473  nbPropagations=1116  nbRevisions=7549  nbUselessRevisions=6187  nbAssignments=44
1.01	     nbFailedAssignments=2  nbBacktracks=2  nbVisitedNodes=49  nbRestartNogoods=0  mapSize=2  nbInferences=0
1.01	     nbTooLargeKeys=0
1.01	       =>  wckTime=0.082  cpuTime=0.06  mem=15M6
1.01	   
1.01	   global
1.01	     nbConstraintChecks=30607  nbPropagations=1981  nbRevisions=12451  nbUselessRevisions=10069  nbRestartNogoods=0
1.01	     solvingWckTime=0.084  solvingCpuTime=0.06  expiredTime=no  totalExploration=no  nbFoundSolutions=1
1.01	     globalCpuTime=0.5
1.01	       =>  wckTime=0.691  cpuTime=0.45  mem=15M6
1.01	   
1.01	s SATISFIABLE
1.01	v 6 0 2 1 4 5 5 7 1 6 6 6 2 5 2 4 4 4 0 6 5 0 6 2 3 0 2 3 5 6 2 2 5 6 3 6 6 1 6 0 
1.01	d NODES 44
1.01	d CHECKS 30607
1.01	   
1.01	   totalWckTime=0.772  totalCpuTime=0.5

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/node2/watcher-227333-1168277923 -o ROOT/results/node2/solver-227333-1168277923 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/227333-1168277923/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: 2.01 2.03 2.12 4/98 16049
/proc/meminfo: memFree=1629816/2055920 swapFree=4191880/4192956
[pid=16048] ppid=16046 vsize=9748 CPUtime=0
/proc/16048/stat : 16048 (java) D 16046 16048 15707 0 -1 0 637 0 0 0 0 0 0 0 18 0 1 0 176187977 9981952 412 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 10535716 0 2147483391 0 7368 18446744072099781622 0 0 17 1 0 0
/proc/16048/statm: 2487 472 386 14 0 1142 0

[startup+0.104187 s]
/proc/loadavg: 2.01 2.03 2.12 4/98 16049
/proc/meminfo: memFree=1629816/2055920 swapFree=4191880/4192956
[pid=16048] ppid=16046 vsize=914988 CPUtime=0.09
/proc/16048/stat : 16048 (java) R 16046 16048 15707 0 -1 0 2980 0 1 0 8 1 0 0 19 0 8 0 176187977 936947712 2726 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4072936459 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/16048/statm: 228747 2726 1423 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.516261 s]
/proc/loadavg: 2.01 2.03 2.12 4/98 16049
/proc/meminfo: memFree=1629816/2055920 swapFree=4191880/4192956
[pid=16048] ppid=16046 vsize=915328 CPUtime=0.5
/proc/16048/stat : 16048 (java) R 16046 16048 15707 0 -1 0 6287 0 1 0 47 3 0 0 18 0 8 0 176187977 937295872 6026 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4153819584 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/16048/statm: 228832 6026 2137 14 0 215302 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 1.04242
CPU time (s): 1.00585
CPU user time (s): 0.949855
CPU system time (s): 0.055991
CPU usage (%): 96.4918
Max. virtual memory (cumulated for all children) (KiB): 915584

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.949855
system time used= 0.055991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8798
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= 1030
involuntary context switches= 1065

runsolver used 0.003999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Mon Jan  8 17:38:43 UTC 2007


IDJOB= 227333
IDBENCH= 6070
FILE ID= node2/227333-1168277923

PBS_JOBID= 3483105

Free space on /tmp= 66337 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.1/rand-2-40-8-753-100-5_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/227333-1168277923/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-227333-1168277923 -o ROOT/results/node2/solver-227333-1168277923 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/227333-1168277923/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  789bb21c78bc2729112e91a1dfccd5a4

RANDOM SEED= 284014609

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.259
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	: 5931.00
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.259
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:       1630296 kB
Buffers:         42476 kB
Cached:         157360 kB
SwapCached:        288 kB
Active:         297432 kB
Inactive:        78868 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1630296 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            1788 kB
Writeback:           0 kB
Mapped:         204680 kB
Slab:            33580 kB
Committed_AS:  5346376 kB
PageTables:       2656 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= 66337 MiB



End job on node2 on Mon Jan  8 17:38:44 UTC 2007