7.3.9. cache_limit — Groonga v16.0.5 documentation

Skip to main content
`Ctrl`+`K`

# 7.3.9. `cache_limit`

## 7.3.9.1. Summary

`cache_limit` gets or sets the max number of query cache entries. Query cache is used only by select command.

If the max number of query cache entries is 100, the recent 100 `select` commands are only cached. The cache expire algorithm is LRU (least recently used).

## 7.3.9.2. Syntax

This command takes only one optional parameter:

    cache_limit [max=null]

## 7.3.9.3. Usage

You can get the current max number of cache entries by executing `cache_limit` without parameter.

Execution example:

    cache_limit
    # [[0,1337566253.89858,0.000355720520019531],100]

You can set the max number of cache entries by executing `cache_limit` with `max` parameter.

Here is an example that sets `10` as the max number of cache entries.

Execution example:

    cache_limit 10
    # [[0,1337566253.89858,0.000355720520019531],100]
    cache_limit
    # [[0,1337566253.89858,0.000355720520019531],10]

If `max` parameter is used, the return value is the max number of cache entries before `max` parameter is set.

## 7.3.9.4. Parameters

This section describes all parameters.

### 7.3.9.4.1. `max`

Specifies the max number of query cache entries as a number.

If `max` parameter isn’t specified, the current max number of query cache entries isn’t changed. `cache_limit` just returns the current max number of query cache entries.

## 7.3.9.5. Return value

`cache_limit` returns the current max number of query cache entries:

    [HEADER, N_ENTRIES]

`HEADER`

> See Output format about `HEADER`.

`N_ENTRIES`

> `N_ENTRIES` is the current max number of query cache entries. It is a number.

## 7.3.9.6. See also

- select