A performant cache for logging systems. CacheAdvance persists log events 30x faster than SQLite.
let myCache = try CacheAdvance<MyMessageType>(
CADCacheAdvance *const cache = [[CADCacheAdvance alloc]
To begin caching messages, you need to create a CacheAdvance instance with:
FileManager's createFile(atPath:contents:attributes:) API.
false. If you care only about preserving recent messages, set this value to
try myCache.append(message: someMessage)
[cache appendMessage:someData error:nil];
By the time the above method exits, the message will have been persisted to disk. A CacheAdvance keeps no in-memory buffer. Appending a new message is cheap, as a CacheAdvance needs to encode and persist only the new message and associated metadata.
A CacheAdvance instance that does not overwrite old messages will throw a
CacheAdvanceError.messageDataTooLarge if appending a message would exceed the cache's
maximumBytes. A CacheAdvance instance that does overwrite old messages will throw a
CacheAdvanceError.messageDataTooLarge if the message would require more than
maximumBytes to store even after evicting all older messages from the cache.
To ensure that caches can be read from 32bit devices, messages should not be larger than 2GB in size.
let cachedMessages = try myCache.messages()
NSArray<NSData> *const cachedMessages = [cache messagesAndReturnError:nil];
This method reads all cached messages from disk into memory.
CacheAdvances are not thread safe: a single CacheAdvance instance should always be interacted with from a single, serial queue. Since CacheAdvance reads from and writes to the disk synchronously, it is best to interact with a CacheAdvance on a background queue to prevent blocking the main queue.
A CacheAdvance will never fatal error: only recoverable errors will be thrown. A CacheAdvance may throw a
CacheAdvanceError, or errors related to reading or writing with
CacheAdvanceError.fileCorrupted error is thrown, the cache file is corrupt and should be deleted.
CacheAdvance immediately persists each appended messages to disk using
FileHandles. Messages are encoded into
Data using a
JSONEncoder by default, though the encoding/decoding mechanism can be customized. Messages are written to disk as an encoded data blob that is prefixed with the length of the message. The length of a message is stored using a
UInt32 to ensure that the size of the data on disk that stores a message's length is consistent between devices.
The first 64bytes of a CacheAdvance is reserved for storing metadata about the file. Any configuration data that must be static between cache opens should be stored in this header. It is also reasonable to store mutable information in the header, if doing so speeds up reads or writes to the file. The header format is managed by FileHeader.swift.
To install CacheAdvance in your iOS project with Swift Package Manager, the following lines can be added to your
.package(url: "https://github.com/dfed/CacheAdvance", from: "2.0.0"),
To install CacheAdvance in your iOS project with CocoaPods, add the following to your
platform :ios, '13.0'
pod 'CacheAdvance', '~> 2.0'
To use git submodules, checkout the submodule with
git submodule add [email protected]:dfed/CacheAdvance.git, drag CacheAdvance.xcodeproj to your project, and add CacheAdvance as a build dependency.
I’m glad you’re interested in CacheAdvance, and I’d love to see where you take it. Please read the contributing guidelines prior to submitting a Pull Request.
Thanks, and happy caching!
Package.swift in the root of the repository to open the project in Xcode.
The default branch of this repository is
main. Between the initial commit and
151ab3f, the default branch of this repository was
master. See #46 for more details on why this change was made.
Shout out to Peter Westen who inspired the creation of this library.
Big thanks to Michael Bachand who has reviewed nearly every change to this library over the years.