Currently all data associated with a datasource are written to the same path within the git file store. This can be further divided by another level of key (see https://github.com/jptmoore/zest/issues/9) but could also internally be divided through time-based buckets/bins to further restrict the amount of data to one path. Needs investigating in terms of performance on a pi3.
Currently all data associated with a datasource are written to the same path within the git file store. This can be further divided by another level of key (see https://github.com/jptmoore/zest/issues/9) but could also internally be divided through time-based buckets/bins to further restrict the amount of data to one path. Needs investigating in terms of performance on a pi3.