1,938 karma · joined September 7, 2011
gmail: max.t.mcdonnell
github.com/maxmcd
GlassDB is much more accessible for smaller volume workloads, but gets very costly for high volume because of requests to S3 per-transaction. In-turn the consistency model is easier to reason about because the system is entirely stateless.
class Lock {
#release: () => void | undefined;
constructor(public name: string) {}
acquire() {
if (this.#release !== undefined) throw new Error("Already locked");
navigator.locks.request(this.name, async (lock) => {
await new Promise<void>(resolve => {
this.#release = resolve;
});
});
}
release() {
if (this.#release === undefined) throw new Error("Not locked");
this.#release();
}
}I can imagine this product is a very elegant solution for many types of companies/teams/workloads.
https://slatedb.io/ is new and KV on object storage. Maybe helpful.
There is lots of similar work over ipfs, I have not had the chance to experiment yet, but I'd like to see what a workflow is like with (eg): summa: https://github.com/izihawa/summa
I tried to implement trigram search on object storage using Zoekt: https://github.com/sourcegraph/zoekt, but I found that common queries load 30-40% of the entire index, so setting it up without some kind of caching strategy felt a little ridiculous.
I do not think languages/runtimes typically implement that kind of prioritization/limiting mechanism.
If you don't need to stream data it is excellent.
ECRS is a program run by ERCOT, they trigger the battery discharge directly, or in some situations the resources might respond to an under-frequency relay.
I imagine the other ERCOT demand response programs were also dispatched.
Other contenders I find myself sharing and re-reading:
- https://swtch.com/~rsc/regexp/regexp1.html
- https://swtch.com/~rsc/regexp/regexp4.html
Sorry, this is all from memory of just having `btop` open for some of the benchmarks. Maybe in a future post I will dig into CPU utlization more.
In the meantime the discussion on lobste.rs includes some lower-level speculation: https://lobste.rs/s/tr8ozm/why_is_spawning_new_process_node_...
I wonder if this kind of service could be implemented without needing to trust the host at all?