cachegrand
varnish-cache
Our great sponsors
| cachegrand | varnish-cache | |
|---|---|---|
| 24 | 5 | |
| 963 | 3,497 | |
| - | 1.4% | |
| 8.0 | 9.7 | |
| 6 months ago | 2 days ago | |
| C | C | |
| BSD 3-clause "New" or "Revised" 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.
cachegrand
-
C++ caching library with tiering (RAM + disc)
Closest that comes to my mind is CacheGrand. It doesn’t have some of the features yet, but I believe @daniele_dll is working on it!
-
[PC][Switzerland] Cheap Rackspace
I use this HW for benchmarking and testing my open source project cachegrand ( https://github.com/danielealbano/cachegrand)
- cachegrand
-
Cachegrand, a fast, Redis compatible, KV store – hashtable documentation
https://github.com/danielealbano/cachegrand/blob/main/docs/a...
When tested with memtier_benchmark, using the Redis protocol, cachegrand itself, on the benchmarking hardware, thanks to the implemented hashtable can reach up to 5 million GET op/s and up to 4.5 million UPSERT op/s without batching, with it up to 60 million GET op/s and up to 26 million UPSERT op/s!
- cachegrand - a blazing fast, Redis compatible, Key-Value store builf for today's hardware - hashtable documentation - capable of delivering up to 112 GET mop/s and 85 UPSERT mop/s on a EPYC 7502P
- Show HN: Cachegrand – a fast OSS Key-Value store built for modern hardware
- Cachegrand – a modern OSS Key-Value store built for today's hardware
varnish-cache
-
FFI and custom (non-global) allocator
I'm having a little bit of a problem trying to wrap my head around wrapping varnish's workspace API in rust.
- AmigaOS afficinado in the dev team .... :-)
-
Simple Linux kernel memory corruption bug leads to complete system compromise
A handful of C projects I have seen use magic numbers in allocated structs to prevent use-after-free and other memory bugs. Basically, in this case, when the ref count hits zero and the struct is freed, the magic is zeroed and any further access will be stopped. The author makes no reference of this, so I guess this isn’t a widespread safety pattern?
Ex: https://github.com/varnishcache/varnish-cache/blob/4ae73a5b1...
-
What the Fastly outage can teach us about writing error messages
Looks like it, except that Varnish has it spelled “Guru Meditation”, not “Guru Mediation”. Anyone know why that would be?
https://github.com/varnishcache/varnish-cache/search?q=medit...
- Fastly Outage
What are some alternatives?
dragonfly - A modern replacement for Redis and Memcached
Alternative PHP Cache (APC) - Alternative PHP Cache
examples - Example data structures and algorithms
Flutter - Flutter makes it easy and fast to build beautiful apps for mobile and beyond
midi-redis - A toy memory store with great performance
hitch - A scalable TLS proxy by Varnish Software.
async-std - Async version of the Rust standard library
hackage-server - Hackage-Server: A Haskell Package Repository
webdis - A Redis HTTP interface with JSON output
fastlane - 🚀 The easiest way to automate building and releasing your iOS and Android apps
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
r_rational - r/rational archived in plain-text org-mode (good for, e.g., doing offline full-text searches)