Package com.arangodb.entity

Class CursorStats

  • public final class CursorStats
extends Object

    • Constructor Detail

      • CursorStats

        public CursorStats()

    • Method Detail

      • getWritesExecuted

        public Long getWritesExecuted()
        Returns:
        The total number of data-modification operations successfully executed.

      • getWritesIgnored

        public Long getWritesIgnored()
        Returns:
        The total number of data-modification operations that were unsuccessful, but have been ignored because of the ignoreErrors query option.

      • getScannedFull

        public Long getScannedFull()
        Returns:
        The total number of documents iterated over when scanning a collection without an index. Documents scanned by subqueries are included in the result, but operations triggered by built-in or user-defined AQL functions are not.

      • getScannedIndex

        public Long getScannedIndex()
        Returns:
        The total number of documents iterated over when scanning a collection using an index. Documents scanned by subqueries are included in the result, but operations triggered by built-in or user-defined AQL functions are not.

      • getCursorsCreated

        public Long getCursorsCreated()
        Returns:
        The total number of cursor objects created during query execution. Cursor objects are created for index lookups.

      • getCursorsRearmed

        public Long getCursorsRearmed()
        Returns:
        The total number of times an existing cursor object was repurposed. Repurposing an existing cursor object is normally more efficient compared to destroying an existing cursor object and creating a new one from scratch.

      • getCacheHits

        public Long getCacheHits()
        Returns:
        The total number of index entries read from in-memory caches for indexes of type edge or persistent. This value is only non-zero when reading from indexes that have an in-memory cache enabled, and when the query allows using the in-memory cache (i.e. using equality lookups on all index attributes).

      • getCacheMisses

        public Long getCacheMisses()
        Returns:
        The total number of cache read attempts for index entries that could not be served from in-memory caches for indexes of type edge or persistent. This value is only non-zero when reading from indexes that have an in-memory cache enabled, the query allows using the in-memory cache (i.e. using equality lookups on all index attributes) and the looked up values are not present in the cache.

      • getFiltered

        public Long getFiltered()
        Returns:
        The total number of documents removed after executing a filter condition in a FilterNode or another node that post-filters data. Note that nodes of the IndexNode type can also filter documents by selecting only the required index range from a collection, and the filtered value only indicates how much filtering was done by a post filter in the IndexNode itself or following FilterNode nodes. Nodes of the EnumerateCollectionNode and TraversalNode types can also apply filter conditions and can report the number of filtered documents.

      • getHttpRequests

        public Long getHttpRequests()
        Returns:
        The total number of cluster-internal HTTP requests performed.

      • getFullCount

        public Long getFullCount()
        Returns:
        The total number of documents that matched the search condition if the query’s final top-level LIMIT operation were not present. This attribute may only be returned if the fullCount option was set when starting the query and only contains a sensible value if the query contains a LIMIT operation on the top level.

      • getExecutionTime

        public Double getExecutionTime()
        Returns:
        The query execution time (wall-clock time) in seconds.

      • getPeakMemoryUsage

        public Long getPeakMemoryUsage()
        Returns:
        The maximum memory usage of the query while it was running. In a cluster, the memory accounting is done per shard, and the memory usage reported is the peak memory usage value from the individual shards. Note that to keep things lightweight, the per-query memory usage is tracked on a relatively high level, not including any memory allocator overhead nor any memory used for temporary results calculations (e.g. memory allocated/deallocated inside AQL expressions and function calls).