Trace number 210352

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.904862 0.926476

DiagnosticValue
CHECKS2585
NODES0

General information on the benchmark

NamepseudoSeries/fpga/
fpga-12-11.xml
MD5SUM8d909165ba3406e0f186f929f5d58d4e
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.135979
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables198
Number of constraints166
Maximum constraint arity12
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension166
Global constraints used (with number of constraints)

Solver Data (download as text)

0.31	   
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/210352-1168197024/unknown.xml
0.38	   
0.38	   domains being loaded...
0.38	   
0.38	   variables being loaded...
0.43	     nbVariables=198  nbDomainTypes=1  minDomainSize=2  maxDomainSize=2
0.43	       =>  wckTime=0.111  cpuTime=0.1  mem=6M951
0.43	   
0.43	   predicates being loaded...
0.44	   
0.44	   constraints being loaded...
0.61	     nbConstraints=166  nbConflictsStructures=5  nbSharedConflictsStructures=161  nbSharedBinaryRepresentations=0
0.61	     nbEvaluationManagers=5  nbSharedEvaluationManagers=161  maxDegree=12  maxArity=12
0.61	       =>  wckTime=0.294  cpuTime=0.21  mem=10M852
0.65	   
0.65	   solver IterativeSystematicSolver being built... 
0.85	       =>  wckTime=0.534  cpuTime=0.38  mem=17M669
0.90	   
0.90	   preprocessing
0.90	     nbConstraintChecks=2585  nbValidityChecks=1360  nbPropagations=498  nbRevisions=1090  nbUselessRevisions=988
0.90	     nbSingletonTests=198  nbEffectiveSingletonTests=0  nbESACBranches=1  nbRemovedValues=0  detectedInconsistency=no
0.90	       =>  wckTime=0.046  cpuTime=0.03  mem=17M669
0.90	   
0.90	   global
0.90	     nbConstraintChecks=2585  nbValidityChecks=1360  nbPropagations=498  nbRevisions=1090  nbUselessRevisions=988
0.90	     nbRestartNogoods=0  solvingWckTime=0.047  solvingCpuTime=0.03  expiredTime=no  totalExploration=no
0.90	     nbFoundSolutions=1  globalCpuTime=0.46
0.90	       =>  wckTime=0.583  cpuTime=0.41  mem=17M669
0.90	   
0.90	s SATISFIABLE
0.90	v 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 
0.90	d NODES 0
0.90	d CHECKS 2585
0.90	   
0.90	   totalWckTime=0.664  totalCpuTime=0.46

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/node24/watcher-210352-1168197024 -o ROOT/results/node24/solver-210352-1168197024 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/210352-1168197024/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.00 1.99 1.99 4/86 24436
/proc/meminfo: memFree=1382760/2055920 swapFree=4192812/4192956
[pid=24435] ppid=24433 vsize=18540 CPUtime=0
/proc/24435/stat : 24435 (runsolver) R 24433 24435 23720 0 -1 4194368 17 0 0 0 0 0 0 0 19 0 1 0 168097686 18984960 279 18446744073709551615 4194304 4267372 548682068960 18446744073709551615 237788261671 0 2147483391 4096 24578 0 0 0 17 1 0 0
/proc/24435/statm: 4635 279 244 17 0 2626 0

[startup+0.103139 s]
/proc/loadavg: 2.00 1.99 1.99 4/86 24436
/proc/meminfo: memFree=1382760/2055920 swapFree=4192812/4192956
[pid=24435] ppid=24433 vsize=913236 CPUtime=0.09
/proc/24435/stat : 24435 (java) R 24433 24435 23720 0 -1 0 2921 0 1 0 8 1 0 0 18 0 8 0 168097686 935153664 2667 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4072925578 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/24435/statm: 228309 2667 1397 14 0 215208 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 913236

[startup+0.511182 s]
/proc/loadavg: 2.00 1.99 1.99 4/86 24436
/proc/meminfo: memFree=1382760/2055920 swapFree=4192812/4192956
[pid=24435] ppid=24433 vsize=915328 CPUtime=0.49
/proc/24435/stat : 24435 (java) R 24433 24435 23720 0 -1 0 6717 0 1 0 46 3 0 0 18 0 8 0 168097686 937295872 6456 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4155839970 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/24435/statm: 228832 6456 2144 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.926476
CPU time (s): 0.904862
CPU user time (s): 0.833873
CPU system time (s): 0.070989
CPU usage (%): 97.6671
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.833873
system time used= 0.070989
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9357
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= 880
involuntary context switches= 877

runsolver used 0.004999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node24 on Sun Jan  7 19:10:24 UTC 2007


IDJOB= 210352
IDBENCH= 4613
FILE ID= node24/210352-1168197024

PBS_JOBID= 3479458

Free space on /tmp= 66471 MiB

BENCH NAME= HOME/pub/bench/CPAI06/pseudoSeries/fpga/fpga-12-11.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/210352-1168197024/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-210352-1168197024 -o ROOT/results/node24/solver-210352-1168197024 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/210352-1168197024/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  8d909165ba3406e0f186f929f5d58d4e

RANDOM SEED= 397416733

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.234
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.234
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:       1383176 kB
Buffers:         59960 kB
Cached:         482816 kB
SwapCached:          0 kB
Active:         262308 kB
Inactive:       341168 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1383176 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1700 kB
Writeback:           0 kB
Mapped:          83132 kB
Slab:            54044 kB
Committed_AS:  3468980 kB
PageTables:       2320 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= 66471 MiB



End job on node24 on Sun Jan  7 19:10:25 UTC 2007