File data
When reading data from a data source, Archil automatically caches it in the high-speed storage layer. Cached data remains active for up to 1 hour after your last access. Writes are buffered in the high-speed storage layer for coalescing before being flushed to the data source. Recently written data remains active for up to 1 hour after it has been flushed. The amount of active data may not exactly match the amount you’ve read or written. Archil prefetches and caches data ahead of sequential reads, which can result in additional cached data. Rapid overwrites to the same file will also result in additional active data while Archil asynchronously coalesces and flushes the writes.File metadata
Metadata accesses (e.g.,find, ls, stat) do not cause file data to become active and incur
no active-storage charges.
Metadata writes (e.g., rename, chmod) are counted as 32 KiB of active data per operation until
the change is propagated to the data source.
Taking ownership of a path with archil checkout lets Archil
coalesce the many small attribute updates a workload produces into larger chunks before metering
them. For example, git clone-ing a 15 MB repository into a checked-out directory is metered as
roughly fifteen 1 MiB writes rather than the thousands of individual metadata operations the client
issues.