public class BOpStats extends Object implements Serializable
BOp
. These statistics
are per BOp
. The top-level BOp
will reflect the throughput
for the entire pipeline.Modifier and Type | Field and Description |
---|---|
CAT |
chunksIn
#of chunks in.
|
CAT |
chunksOut
#of chunks out.
|
CAT |
elapsed
The elapsed time (milliseconds) for the corresponding operation.
|
CAT |
mutationCount
The #of tuples written onto a relation (not an index).
|
CAT |
opCount
The #of instances of a given operator which have been started (and
successully terminated) for a given query.
|
CAT |
typeErrors
The #of error which were masked by the semantics of the query.
|
CAT |
unitsIn
#of units sets in (tuples, elements, binding sets, etc).
|
CAT |
unitsOut
#of units sets in (tuples, elements, binding sets, etc).
|
Constructor and Description |
---|
BOpStats()
Constructor.
|
Modifier and Type | Method and Description |
---|---|
void |
add(BOpStats o)
Combine the statistics (addition), but do NOT add to self.
|
String |
toString() |
protected void |
toString(StringBuilder sb)
Extension hook for
toString() . |
public final CAT elapsed
public final CAT opCount
public final CAT chunksIn
public final CAT unitsIn
public final CAT chunksOut
public final CAT unitsOut
public final CAT typeErrors
Note: SPARQL type errors in aggregations often cause bindings or solutions to fail without causing any runtime exception which can be observed at the query level. This counter provides a means to observe those errors.
public final CAT mutationCount
Note: This mutation counts should reflect the #of tuples written on a relation rather than on an index. The per-index tuple mutation count MAY also be reported, but it should be reported by extending this class and declaring additional mutation counters.
Note: Operations which fix point some closure depend on the correctness
of the mutationCount
for their termination condition.
Note: Mutation operations MUST NOT overwrite existing tuples with
identical state. This is important for two reasons. First, fix point
operations depend on the mutationCount
being ZERO (0) in a given
round if nothing was changed in order to terminate the closure. Second,
due to the general MVCC and copy-on-write architecture, index writes
drive IO. If the tuple state would not be changed, then the index write
SHOULD NOT be performed.
public BOpStats()
Note: Do not pre-increment opCount
. See add(BOpStats)
and AbstractRunningQuery.haltOp(IHaltOpMessage)
.
public void add(BOpStats o)
o
- Another statistics object.protected void toString(StringBuilder sb)
toString()
.sb
- Where to write the additional state.Copyright © 2006–2019 SYSTAP, LLC DBA Blazegraph. All rights reserved.