komuW
Joined 9 years ago
Karma
914
Submissions
113
Member since
Aug 15
Recent submissions
Comment · 1 year ago
Take a look at FSRS.
The paper: https://dl.acm.org/doi/10.1145/3534678.3539081?cid=996605471...
Various implementations: https://github.com/open-spaced-repetition/awesome-fsrs
Some benchmarks of various srs algorithms: https://expertium.github.io/Benchmark.html
Comment · 2 years ago
Have you looked at Tyk? https://github.com/TykTechnologies/tyk/
Comment · 2 years ago
Location: Nairobi, Kenya
Remote: Yes
Willing to relocate: No
Technologies: Golang, Python, Django, SQL, PostgreSQL, AWS
Résumé/CV: https://www.komu.engineer/cv/komu-CV.pdf
Email: [email protected]
Blog: https://www.komu.engineer/blog
I'm a software engineer with ~8yrs experience. Here's somethings that I've done;
- Reduced cloud costs for a production kubernetes service by 20%. This was done by analysing pod utilisation on kubernetes and then right-sizing the pods to match the expected usage.
- Read the SMPP specification and implemented a client for it from scratch. Integrated the client into a production application and used it to send out SMS at averaget rates of 800/second.
- Created an open source ACME client based off the ACME specification.
Comment · 2 years ago
Hi, could you guys please reply to job applications. I had applied in April and up to now I haven't received even a rejection email.
Comment · 2 years ago
My solution[1] to this problem is to do what they did in the Apollo Guidance Computer; log to a ring buffer and only flush it (to disk or wherever) on certain conditions.
1. https://www.komu.engineer/blogs/09/log-without-losing-contex...
Comment · 2 years ago
Nice article. If you ever wondered how the python equivalent(celery) works, I wrote a blogpost about that ~4years ago; https://www.komu.engineer/blogs/07/understand-how-celery-wor...
Comment · 3 years ago
My favorite technique for reducing the cost of logging is the same technique that was employed in The Apollo Guidance Computer(though I'm not sure if they did it for cost purposes).
To quote from Annotations to Eldon Hall's Journey to the Moon[1]: "The Coroner recorded every instruction executed, with its inputs and results, writing over the oldest record when it filled up. When a program crashed, you could punch out a full record of what it was doing in most of its last second and analyze the problem at your ease. I have often wished that PCs offered such an advanced feature."
So essentially buffer all logs into an in-memory circular buffer of capacity N. If a log record is emitted that has a certain severity/level; flush all records from the buffer to disk/clickHouse/grafana/whatever.
The python MemoryHandler[2] almost implements the said technique, except that it also flushes when buffer is full; which is not particularly what I would want.
I also wrote a blogpost[3] about how to log without losing money or context, ~3yrs ago.
1. https://authors.library.caltech.edu/5456/1/hrst.mit.edu/hrs/...
2. https://github.com/python/cpython/blob/v3.11.1/Lib/logging/h...
3. https://www.komu.engineer/blogs/09/log-without-losing-contex...
https://www.komu.engineer
work: https://dushed.com email: komuw05 @ google's mail thingy .com