thinkingfish

5 ms·

1.
by thinkingfish 3y ago
We also published it as a crate https://crates.io/crates/segcache
2.
Fighting off fake-serverless bandits with the true definition of serverless(gomomento.com)
1 points by thinkingfish 4y ago|0 comments
3.
by thinkingfish 4y ago
What’s your billing model?
4.
by thinkingfish 4y ago
Congrats! Although I look back fondly on the many years I spent on debugging cache incidents ( https://danluu.com/cache-incidents/ ) I don’t think the rest of the world should go through the same bumpy road. It’s truly i
5.
by thinkingfish 4y ago
Hello! I still have your cookie jar LOL
6.
by thinkingfish 4y ago
Hopefully we can open source our deployment "generator" sometime soon. It's not gonna work in AWS (Twitter isn't a cloud first company) but you will get the basic idea. Yes, swappable storage backend is a big driver of t
7.
by thinkingfish 4y ago
It was supposed to be a bit tongue-in-cheek... Obviously nobody should create a pingserver just for the sake of with the specs we had. But, as a halfway marker to a production-ready cache service, it's good to have something that lets
8.
by thinkingfish 4y ago
They are not quite the same thing. Pelikan has the building blocks for an RPC server, storage, wire protocols, data structures, and whatever code that is needed to glue these together in some form to provide functionalities as a service (wh
9.
by thinkingfish 4y ago
I assume you meant this as a comparison against Segcache? We touched upon the CLOCK-Pro a bit in related work of the paper ( https://www.usenix.org/system/files/nsdi21-yang.pdf , Section 6.1). I haven't done a
10.
by thinkingfish 4y ago
It's a SaaS startup offering managed cache (like Elastic Cache). They have their own protocol but uses Pelikan-segcache as one of their backends.
11.
by thinkingfish 4y ago
I'm a big fan of their fountain pens and the piston filling mechanism.
12.
by thinkingfish 4y ago
Project creator here, didn't expect to see the link on HN :P Here's the latest code architecture diagram: https://raw.githubusercontent.com/pelikan-io/pelikan-io.gith... And a slightly outdated but mostly acc
13.
by thinkingfish 5y ago
Oh the link broke when I changed the permanent URL format after the post was published. Here is the correct link: https://twitter.github.io/pelikan/2016/separation-concerns.h... I've fixed the post as well, t
14.
by thinkingfish 5y ago
Disclosure: I'm maintainer/author of Pelikan. I wrote about Pelikan, a unified cache framework, and its relationship to Memcached and Redis in this blog from 2019: https://twitter.github.io/pelikan/2019/w
15.
by thinkingfish 5y ago
Here’s a blog version of the paper for anybody who isn’t into 12 page double column pdf files https://twitter.github.io/pelikan/2021/segcache.html
16.
by thinkingfish 5y ago
Internally I’ve written a generator to spit out a deploy config based on input vectors such as (qps, data size, connections). But it assumes using Twitter’s container environment. Publicly I think I want to do two things: 1. write a blog ab
17.
by thinkingfish 5y ago
lol I'm glad you asked there since I am on HN about once every 3 months...
18.
by thinkingfish 5y ago
Based on his response on Twitter I'd guess not https://twitter.com/dormando/status/1381706098290225152 But also agree with you that in that high concurrency usually not needed when using distributed caching.
19.
by thinkingfish 10y ago
The nature of tech work means employees generally have more flexibility with their time, and can afford such involvement without jeopardizing their productivity or job. It is thus hard to quantify how much money it costs for such engagement
20.
by thinkingfish 10y ago
I don't work on GraphDB, but basically the situation is this: 1) yes, it is not a great use case for MySQL, but that's how it started, partly because Twitter needed join on its graphs; 2) legacy systems die hard, especially at sca
21.
by thinkingfish 10y ago
In general, Twitter infrastructure didn't start by building solutions in house. Like most early stage companies, it started by using whatever it can find in the OSS repertoire. But a lot of problems that are non-existing at a smaller s
22.
Twitter open-sourced Pelikan, a cache framework(twitter.github.io)
1 points by thinkingfish 10y ago|0 comments
23.
by thinkingfish 11y ago
CSCI 3350: Debugging- Beyond Print CSCI 4600: When Big-O Complexity Becomes a Lie and Why
24.
by thinkingfish 11y ago
CSCI 4035: Refactor Your Own Term Projects from Past Semesters
25.
by thinkingfish 11y ago
Would be nice to allow filters- for example, leave out any results that match patterns in .gitignore.
26.
by thinkingfish 14y ago
This is not an issue for fatcache. slab item chunk size introduces internal fragmentation (because items sizes usually don't match "chunk" sizes unless you use slab profile, -z option, to match them up). The kind of external fragmentation y