Trace number 230667

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.928858 1.04992

DiagnosticValue
CHECKS56871
NODES50

General information on the benchmark

Namegeom/
geo50-20-d4-75-88_ext.xml
MD5SUM9ce00c904554c3fc87671e07eba26818
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.102983
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints354
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension354
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.40	   
0.40	Abscon 109 (November, 2006)
0.40	   
0.40	   configuration
0.40	     name=esac.xml
0.44	   
0.44	   instance
0.44	     name=/tmp/evaluation/230667-1168316979/unknown.xml
0.47	   
0.47	   domains being loaded...
0.47	   
0.47	   variables being loaded...
0.51	     nbVariables=50  nbDomainTypes=1  minDomainSize=20  maxDomainSize=20
0.51	       =>  wckTime=0.106  cpuTime=0.08  mem=6M951
0.51	   
0.51	   relations being loaded...
0.63	   
0.63	   constraints being loaded...
0.74	     nbConstraints=354  nbRelationTypes=354  nbExtensionStructures=354  nbSharedExtensionStructures=0
0.74	     nbConflictsStructures=354  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=2992  maxDegree=21
0.74	     maxArity=2
0.74	       =>  wckTime=0.333  cpuTime=0.24  mem=13M794
0.78	   
0.78	   solver IterativeSystematicSolver being built... 
0.94	       =>  wckTime=0.537  cpuTime=0.37  mem=15M165
0.99	   
0.99	   preprocessing
0.99	     nbConstraintChecks=40643  nbPropagations=759  nbRevisions=4355  nbUselessRevisions=3566  nbSingletonTests=82
0.99	     nbEffectiveSingletonTests=0  nbESACBranches=3  nbRemovedValues=0  detectedInconsistency=no
0.99	       =>  wckTime=0.049  cpuTime=0.03  mem=15M165
1.01	   
1.01	   search
1.02	     run=0  nbConstraintChecks=16228  nbPropagations=1104  nbRevisions=6089  nbUselessRevisions=4972  nbAssignments=50
1.02	     nbFailedAssignments=0  nbBacktracks=0  nbVisitedNodes=51  nbRestartNogoods=0  mapSize=0  nbInferences=0
1.02	     nbTooLargeKeys=0
1.02	       =>  wckTime=0.071  cpuTime=0.05  mem=15M165
1.02	   
1.02	   global
1.02	     nbConstraintChecks=56871  nbPropagations=1863  nbRevisions=10444  nbUselessRevisions=8538  nbRestartNogoods=0
1.02	     solvingWckTime=0.073  solvingCpuTime=0.05  expiredTime=no  totalExploration=no  nbFoundSolutions=1
1.02	     globalCpuTime=0.47
1.02	       =>  wckTime=0.612  cpuTime=0.42  mem=15M165
1.02	   
1.02	s SATISFIABLE
1.02	v 14 4 19 19 12 17 5 5 18 3 16 2 10 13 8 13 20 6 17 4 3 14 3 1 13 9 19 4 4 19 11 6 3 8 9 6 11 12 17 8 6 6 4 8 4 8 2 19 6 13 
1.02	d NODES 50
1.02	d CHECKS 56871
1.02	   
1.02	   totalWckTime=0.696  totalCpuTime=0.47

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/node34/watcher-230667-1168316979 -o ROOT/results/node34/solver-230667-1168316979 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230667-1168316979/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.47 1.13 1.29 4/73 21020
/proc/meminfo: memFree=700216/2055920 swapFree=4192812/4192956
[pid=21019] ppid=21017 vsize=168 CPUtime=0
/proc/21019/stat : 21019 (java) R 21017 21019 18574 0 -1 0 39 0 0 0 0 0 0 0 18 0 1 0 180091654 172032 23 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 7721259 0 0 4096 0 0 0 0 17 0 0 0
/proc/21019/statm: 42 23 18 14 0 2 0

[startup+0.107557 s]
/proc/loadavg: 1.47 1.13 1.29 4/73 21020
/proc/meminfo: memFree=700216/2055920 swapFree=4192812/4192956
[pid=21019] ppid=21017 vsize=906644 CPUtime=0.03
/proc/21019/stat : 21019 (java) R 21017 21019 18574 0 -1 0 2125 0 14 0 2 1 0 0 18 0 2 0 180091654 928403456 1887 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4153609883 0 4 0 7368 18446744073709551615 0 0 17 1 0 0
/proc/21019/statm: 226661 1887 1070 14 0 214244 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 906644

[startup+0.515594 s]
/proc/loadavg: 1.47 1.13 1.29 4/73 21020
/proc/meminfo: memFree=700216/2055920 swapFree=4192812/4192956
[pid=21019] ppid=21017 vsize=915328 CPUtime=0.41
/proc/21019/stat : 21019 (java) R 21017 21019 18574 0 -1 0 6106 0 22 0 37 4 0 0 18 0 8 0 180091654 937295872 5866 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 7685315 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/21019/statm: 228832 5866 2137 14 0 215302 0
Current children cumulated CPU time (s) 0.41
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 1.04992
CPU time (s): 0.928858
CPU user time (s): 0.865868
CPU system time (s): 0.06299
CPU usage (%): 88.4697
Max. virtual memory (cumulated for all children) (KiB): 915456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.865868
system time used= 0.06299
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8752
page faults= 22
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 958
involuntary context switches= 974

runsolver used 0.003999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node34 on Tue Jan  9 04:29:39 UTC 2007


IDJOB= 230667
IDBENCH= 6426
FILE ID= node34/230667-1168316979

PBS_JOBID= 3502526

Free space on /tmp= 66550 MiB

BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-88_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230667-1168316979/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node34/watcher-230667-1168316979 -o ROOT/results/node34/solver-230667-1168316979 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230667-1168316979/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  9ce00c904554c3fc87671e07eba26818

RANDOM SEED= 219991789

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.227
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.227
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:        700696 kB
Buffers:          4928 kB
Cached:        1275240 kB
SwapCached:          0 kB
Active:         316092 kB
Inactive:       986252 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        700696 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2320 kB
Writeback:           0 kB
Mapped:          35756 kB
Slab:            38320 kB
Committed_AS:  3197100 kB
PageTables:       1720 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= 66550 MiB



End job on node34 on Tue Jan  9 04:29:40 UTC 2007