jhgg

22 ms·

1.
by jhgg 5mo ago
We just track power utilization.
2.
by jhgg 7mo ago
Cool article :)
3.
by jhgg 11mo ago
Yes, agreed, hence rarely a problem in practice ;)
4.
by jhgg 11mo ago
Risk of deadlock is real if you have processes calling each-other in a cyclic way. e.g. process A sends GenServer call to process B, that then sends a GenServer call to process A to in order to handle the original call. However, process A i
5.
by jhgg 1y ago
> government passes law that requires companies to age verify users > said government provides no way to actually verify a human's age > hilarity ensues
6.
by jhgg 1y ago
Really cool! You looking to write Elixir as your main job?
7.
by jhgg 1y ago
This is not a model issue - you just have not properly implemented acoustic echo cancellation on your end.
8.
by jhgg 1y ago
The truth is this won't actually stop AI crawlers and they'll just move to a large residential proxy pool to work around it. Not sure what the solution is honestly.
9.
by jhgg 1y ago
Sweet! That's much more reasonable!
10.
by jhgg 1y ago
$5 to resize 1,000 images is ridiculously expensive. At my last job we resized a very large amount of images every day, and did so for significantly cheaper (a fraction of a cent for a thousand images). Am I missing something here?
11.
by jhgg 1y ago
IMO, it's not. All the UI boils down to: https://github.com/zhangchenchen/query_gpt/blob/main/src/api...
12.
by jhgg 2y ago
Metal looks super cool, however at my last job when we tried using instance local SSD's on GCP, there were serious reliability issues (e.g. blocks on the device losing data). Has this situation changed? What machine types are you using
13.
by jhgg 2y ago
Hoping this leads to datadog launching a logging solution that does not cost an arm and a leg at scale.
14.
by jhgg 2y ago
Except this article is about how their efforts to prompt the LLM didn't end up working and how they used embeddings / vector search to filter out comments that the LLM generated based on user feedback.
15.
by jhgg 2y ago
Does that matter when you can just swap it for gpt-5-whatever at some point in the future?
16.
by jhgg 2y ago
Are you implying this technology will remain static in its capabilities going forward despite it having seen significant improvement over the last few years?
17.
by jhgg 2y ago
I did this measurement, and using time -v, the maximum resident size in KB comes out to 440,424 kb for 1m tasks, 46,820 kb for 100k, and 7,156 kb for 10k.
18.
by jhgg 2y ago
When I worked at Discord, we used BEAM hot code loading pretty extensively, built a bunch of tooling around it to apply and track hot-patches to nodes (which in turn could update the code on >100M processes in the system.) It allowed us
19.
by jhgg 2y ago
Having a potentially untrusted client connect to the erlang node as a c_node (which seems to be what zerl does) is not a good idea generally, as connecting that way essentially allows the client to execute arbitrary code on the server.
20.
by jhgg 2y ago
https://github.com/discord/sorted_set_nif
21.
by jhgg 2y ago
A content-defined chunking scheme allows for you to build a pretty efficient game patcher where you can update between any version of the game (forwards and backwards) and doesn't require a bunch of server-side shenanigans. League of L
22.
by jhgg 2y ago
Yeah it just worked a lot better on scylla.
23.
by jhgg 2y ago
No cache. Just read coalescing. There is a big difference. Coalescing just ensures that while a query is executing if an identical query arrives, rather than sending the same query as an already executing query to the database it will wait
24.
by jhgg 2y ago
We did not change schema or partitioning strategy.
25.
by jhgg 2y ago
Scylla just eats all the ram it can with cache. So it's hard to say really. On Cassandra we allocated half the ram to the JVM which it gladly used up and left the other half to the OS for disk cache. On Scylla, since it uses direct io,
26.
by jhgg 2y ago
Read traffic is much higher than write traffic due to mobile clients needing to sync chat history more often as their sessions are much shorter lived. Also search queries execute 1 query per result. And don't forget people doing GDPR d
27.
by jhgg 2y ago
Nope. Didn't change the schema, mainly added read coalescing and used ICS. I think the big thing is when Scylla is processing a bunch of tombstones it's able to do so in a way that doesn't choke the whole server. Latest Scyll
28.
by jhgg 2y ago
There are ballpark of a few hundred million discord servers... do you really want to run that many Postgres instances? And even so what do you do about DM/GDMs? Easier to just run one big mega cluster for messages.
29.
by jhgg 2y ago
Fwiw the benchmarked numbers are for writing very small rows. When doing the messages migration, with no read traffic, and the cluster/compaction settings tuned for writes we only managed approx 3m inserts/sec while fully saturati
30.
by jhgg 2y ago
Yes, we wanted to migrate all our data stores away from Cassandra due to stability and performance issues. Moving to something that didn't have those issues (or at least had a different set of less severe issues) while also not having

More ›