AutoBlock-global-settings {DelayedArray} | R Documentation

## Control the geometry of automatic blocks

### Description

A family of utilities to control the automatic block size (or length) and shape.

### Usage

    getAutoBlockSize()
    setAutoBlockSize(size=1e8)

    getAutoBlockLength(type)

    getAutoBlockShape()
    setAutoBlockShape(shape=c("hypercube",
                              "scale",
                              "first-dim-grows-first",
                              "last-dim-grows-first"))

### Arguments

`size` | The auto block size (automatic block size) in bytes. Note that, except when the type of the array data is `"character"` or `"list"`, the size of a block is its length multiplied by the size of an array element. For example, a block of 500 x 1000 x 500 doubles has a length of 250 million elements and a size of 2 Gb (each double occupies 8 bytes of memory). The auto block size is set to 100 Mb at package startup and can be reset anytime to this value by calling `setAutoBlockSize()` with no argument.
`type` | A string specifying the type of the array data.
`shape` | A string specifying the auto block shape (automatic block shape). See `makeCappedVolumeBox` for a description of the supported shapes. The auto block shape is set to `"hypercube"` at package startup and can be reset anytime to this value by calling `setAutoBlockShape()` with no argument.

### Details

block size != block length

block length = number of array elements in a block (i.e. `prod(dim(block))`).

block size = block length * size of the individual elements in memory.

For example, for an integer array, block size (in bytes) is going to be 4 x block length. For a numeric array `x` (i.e. `type(x) == "double"`), it's going to be 8 x block length.

In its current form, block processing in the DelayedArray package must decide the geometry of the blocks before starting the walk on the blocks. It does this based on several criteria. Two of them are:

- The auto block size: maximum size (in bytes) of a block once loaded in memory.

- The `type()` of the array (e.g. `integer`, `double`, `complex`, etc...)

The auto block size setting and `type(x)` control the maximum length of the blocks. Other criteria control their shape. So for example if you set the auto block size to 8GB, this will cap the length of the blocks to 2e9 if your DelayedArray object `x` is of type `integer`, and to 1e9 if it's of type `double`.

Note that this simple relationship between block size and block length assumes that blocks are loaded in memory as ordinary (a.k.a. dense) matrices or arrays. With sparse blocks, all bets are off. But the max block length is always taken to be the auto block size divided by `get_type_size(type())` whether the blocks are going to be loaded as dense or sparse arrays. If they are going to be loaded as sparse arrays, their memory footprint is very likely to be smaller than if they were loaded as dense arrays so this is safe (although probably not optimal).

It's important to keep in mind that the auto block size setting is a simple way for the user to put a cap on the memory footprint of the blocks. Nothing more. In particular it doesn't control the maximum amount of memory used by the block processing algorithm. Other variables can impact dramatically memory usage like parallelization (where more than one block is loaded in memory at any given time), what the algorithm is doing with the blocks (e.g. something like `blockApply(x, identity)` will actually load the entire array data in memory), what delayed operations are on `x`, etc... It would be awesome to have a way to control the maximum amount of memory used by a block processing algorithm as a whole but we don't know how to do that.

### Value

`getAutoBlockSize`: The current auto block size in bytes as a single numeric value.

`setAutoBlockSize`: The new auto block size in bytes as an invisible single numeric value.

`getAutoBlockLength`: The auto block length as a single integer value.

`getAutoBlockShape`: The current auto block shape as a single string.

`setAutoBlockShape`: The new auto block shape as an invisible single string.

### See Also

- `defaultAutoGrid` and family to create automatic grids to use for block processing of array-like objects.

- `blockApply` and family for convenient block processing of an array-like object.

- The `makeCappedVolumeBox` utility to make capped volume boxes.

### Examples

    getAutoBlockSize()

    getAutoBlockLength("double")
    getAutoBlockLength("integer")
    getAutoBlockLength("logical")
    getAutoBlockLength("raw")

    m <- matrix(runif(600), ncol=12)
    setAutoBlockSize(140)
    getAutoBlockLength(type(m))
    defaultAutoGrid(m)
    lengths(defaultAutoGrid(m))
    dims(defaultAutoGrid(m))

    getAutoBlockShape()
    setAutoBlockShape("scale")
    defaultAutoGrid(m)
    lengths(defaultAutoGrid(m))
    dims(defaultAutoGrid(m))

    ## Reset the auto block size and shape to factory settings:
    setAutoBlockSize()
    setAutoBlockShape()

[Package DelayedArray version 0.18.0 Index]