mirror of
https://github.com/Expand-sys/CCash
synced 2025-12-17 00:22:14 +11:00
📚🚧
This commit is contained in:
parent
3650bff3f0
commit
335fd4983c
1 changed files with 12 additions and 5 deletions
|
|
@ -10,9 +10,16 @@ below is `GetBal()` being called where `x` axis grows with # of users reaching 1
|
||||||
.png)
|
.png)
|
||||||
as the graph demonstrates, regardless of size GetBal remains consistent at around 39ns on my 3700x.
|
as the graph demonstrates, regardless of size GetBal remains consistent at around 39ns on my 3700x.
|
||||||
## xxHash
|
## xxHash
|
||||||
## base64
|
## Base64
|
||||||
## simdjson
|
## Simdjson
|
||||||
## drogon webframework
|
## Drogon webframework
|
||||||
## multi-threading support
|
## Multi-threading support
|
||||||
## intelligent saving
|
## Intelligent saving
|
||||||
|
### Saving on close
|
||||||
|
when the program is interupted with CONTROL + C it will save before closing the webserver, **it will not however save during a crash**.
|
||||||
|
### Auto Saving
|
||||||
|
every `x` minutes, a configurable amount at launch, CCash will save.
|
||||||
|
### Changes
|
||||||
|
for the above two cases, it will only save if changes have been made since last commit.
|
||||||
## Backwards Compatible API
|
## Backwards Compatible API
|
||||||
|
versioning is implemented by the endpoints path, for example `/v1`. Breaking changes will ideally be sparse and backwards compatability will be maintained, for example ideally API `v3` instance can still run `v1` endpoints
|
||||||
Loading…
Reference in a new issue