go | act | |
---|---|---|
1 | 2 | |
447 | 188 | |
- | 0.0% | |
0.0 | 3.9 | |
almost 2 years ago | about 2 months ago | |
Go | C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go
-
IceFireDB: Distributed disk storage database based on Raft and Redis protocol
So what "IceFireDB" is:
1. tidwall/uhaha - Raft server
2. tidwall/redcon - Read/write redis protocol
3. ledisdb/ledisdb - Redis-compatible with disk persistence via leveldb
4. syndtr/goleveldb/leveldb - Provides snapshots, other scattered references throughout code
It also includes this seemingly random file below, which seems to implement String/Slice for string/byte using unsafe.Pointer:
https://github.com/siddontang/go/blob/master/hack/hack.go
act
-
Probing My SSD's Latency
The Aerospike ACT benchmarking tool characterizes flash devices on their latency under a fixed read/write profile. It won't tell you how fast your device is, it will tell you if a workload runs under a certain latency bound.
https://docs.aerospike.com/server/operations/plan/ssd/ssd_ce...
https://github.com/aerospike/act
If you set
max-lag-sec: 0
-
IceFireDB: Distributed disk storage database based on Raft and Redis protocol
It depends, yes but ... (not discounting any of the above).
One sees a lot of 3:1 in practice due to the replication factor. If you have 3 copies of the data and the client can read from any node, you get 3x the read performance as having to have a quorum write on two out of three nodes.
To the GP, for a rough swag of what is possible out of given hardware, a combination of FIO and ACT (measures IO latency under a fixed load) is a good start.
https://fio.readthedocs.io/en/latest/fio_doc.html
https://github.com/aerospike/act
What are some alternatives?
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
IceFireDB - @IceFireLabs -> IceFireDB is a database built for web3.0 It strives to fill the gap between web2 and web3.0 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.
fio - Flexible I/O Tester