Trace number 203881

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.08883 1.13314

DiagnosticValue
CHECKS16547511
NODES0

General information on the benchmark

Namedomino/
domino-100-300.xml
MD5SUM81d875c326584bd3cb1f81dea50bea7a
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.020996
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints100
Maximum constraint arity2
Maximum domain size300
Number of constraints which are defined in extension0
Number of constraints which are defined in intension100
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/203881-1168164960/unknown.xml
0.39	   
0.39	   domains being loaded...
0.39	   
0.39	   variables being loaded...
0.44	     nbVariables=100  nbDomainTypes=1  minDomainSize=300  maxDomainSize=300
0.44	       =>  wckTime=0.117  cpuTime=0.09  mem=7M929
0.44	   
0.44	   predicates being loaded...
0.44	   
0.44	   constraints being loaded...
0.59	     nbConstraints=100  nbConvertedConstraints=100  nbConvertConstraintsChecks=180000  nbExtensionStructures=2
0.59	     nbSharedExtensionStructures=98  nbConflictsStructures=2  nbSharedConflictsStructures=98
0.59	     nbSharedBinaryRepresentations=898  maxDegree=2  maxArity=2
0.59	       =>  wckTime=0.263  cpuTime=0.21  mem=8M937
0.63	   
0.63	   solver IterativeSystematicSolver being built... 
0.81	       =>  wckTime=0.484  cpuTime=0.36  mem=15M490
1.09	   
1.09	   preprocessing
1.09	     nbConstraintChecks=16547511  nbPropagations=30001  nbRevisions=30100  nbUselessRevisions=200  nbSingletonTests=100
1.09	     nbEffectiveSingletonTests=0  nbESACBranches=1  nbRemovedValues=29900  detectedInconsistency=no
1.09	       =>  wckTime=0.274  cpuTime=0.25  mem=15M490
1.09	   
1.09	   global
1.09	     nbConstraintChecks=16547511  nbPropagations=30001  nbRevisions=30100  nbUselessRevisions=200  nbRestartNogoods=0
1.09	     solvingWckTime=0.275  solvingCpuTime=0.25  expiredTime=no  totalExploration=no  nbFoundSolutions=1
1.09	     globalCpuTime=0.67
1.09	       =>  wckTime=0.764  cpuTime=0.61  mem=15M490
1.09	   
1.09	s SATISFIABLE
1.09	v 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 299 
1.09	d NODES 0
1.09	d CHECKS 16547511
1.09	   
1.09	   totalWckTime=0.854  totalCpuTime=0.67

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/node38/watcher-203881-1168164960 -o ROOT/results/node38/solver-203881-1168164960 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/203881-1168164960/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: 1.92 1.99 1.82 4/81 10898
/proc/meminfo: memFree=1527936/2055920 swapFree=4192812/4192956
[pid=10897] ppid=10895 vsize=18540 CPUtime=0
/proc/10897/stat : 10897 (runsolver) R 10895 10897 9845 0 -1 4194368 17 0 0 0 0 0 0 0 18 0 1 0 164895672 18984960 279 18446744073709551615 4194304 4267372 548682068960 18446744073709551615 266890439975 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/10897/statm: 4635 279 244 17 0 2626 0

[startup+0.107414 s]
/proc/loadavg: 1.92 1.99 1.82 4/81 10898
/proc/meminfo: memFree=1527936/2055920 swapFree=4192812/4192956
[pid=10897] ppid=10895 vsize=914988 CPUtime=0.09
/proc/10897/stat : 10897 (java) R 10895 10897 9845 0 -1 0 3011 0 1 0 8 1 0 0 20 0 8 0 164895672 936947712 2757 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4155239840 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/10897/statm: 228747 2757 1433 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.515489 s]
/proc/loadavg: 1.92 1.99 1.82 4/81 10898
/proc/meminfo: memFree=1527936/2055920 swapFree=4192812/4192956
[pid=10897] ppid=10895 vsize=915460 CPUtime=0.49
/proc/10897/stat : 10897 (java) R 10895 10897 9845 0 -1 0 6606 0 1 0 44 5 0 0 18 0 8 0 164895672 937431040 6345 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4072941368 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/10897/statm: 228865 6345 2165 14 0 215335 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915460

Child status: 0
Real time (s): 1.13314
CPU time (s): 1.08883
CPU user time (s): 1.00985
CPU system time (s): 0.078987
CPU usage (%): 96.0902
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.00985
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= 8808
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= 769
involuntary context switches= 849

runsolver used 0.003999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node38 on Sun Jan  7 10:16:00 UTC 2007


IDJOB= 203881
IDBENCH= 3987
FILE ID= node38/203881-1168164960

PBS_JOBID= 3478571

Free space on /tmp= 66513 MiB

BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-100-300.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/203881-1168164960/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node38/watcher-203881-1168164960 -o ROOT/results/node38/solver-203881-1168164960 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/203881-1168164960/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  81d875c326584bd3cb1f81dea50bea7a

RANDOM SEED= 723293822

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.267
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.267
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:       1528352 kB
Buffers:         54144 kB
Cached:         234788 kB
SwapCached:          0 kB
Active:         291140 kB
Inactive:       164308 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1528352 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            5380 kB
Writeback:           0 kB
Mapped:         185700 kB
Slab:            57040 kB
Committed_AS:  4208884 kB
PageTables:       2244 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= 66513 MiB



End job on node38 on Sun Jan  7 10:16:02 UTC 2007