ConnorLeet (u/ConnorLeet)

ConnorLeet commented on Partitioning Postgres tables by timestamp based UUIDs elixirforum.com/t/partiti... · Posted by u/amalinovic

mewpmewp2 · 2 years ago

Also what I think. And it feels like partitioning would imply much more work and potential future implications rather than figuring out what was the issue with some queries or indexes. Postgres should be able to handle billions of rows.

And if the issue was with the queries per second, it would feel to me like it would still be less disruptive to just have some sort of replication going on for reads.

And partitioning really makes sense to me only if you are going to have it on multiple boxes, because otherwise I don't think there really should be many performance gains compared to just indexing?

I'm not seeing if/how they put it on multiple boxes?

ConnorLeet · 2 years ago

A big benefit of partitioning is being able to drop partitions that expire instead of doing deletes. Assuming you’ll ever need to delete of course!

Deleted Comment

ConnorLeet commented on AlloyDB Omni – run AlloyDB anywhere cloud.google.com/blog/pro... · Posted by u/forrestbrazeal

ellisv · 3 years ago

I haven't tried AlloyDB yet but I've found most of GCP is this way. I've had to perform several Cloud SQL db migrations this year because storage will auto increase (due to ephemerally high tmp_data) and cannot decrease.

Lots of other rough edges with their other services. I have to believe that Google doesn't dog-food their own services.

ConnorLeet · 3 years ago

All clouds do that for databases

ConnorLeet commented on Oxy is Cloudflare's Rust-based next generation proxy framework blog.cloudflare.com/intro... · Posted by u/lukastyrychtr

fl0ps · 3 years ago

They obliviously missed an opportunity to call it "Roxy" and avoid the unfortunate current name collision...

ConnorLeet · 3 years ago

Naming things is hard.

https://www.urbandictionary.com/define.php?term=roxy (2nd entry)

ConnorLeet commented on Hot Reloading Rust – For Fun and Faster Feedback Cycles robert.kra.hn/posts/hot-r... · Posted by u/redbell

nixpulvis · 4 years ago

Just a quick thought... wouldn't it be a bit more practical to implement this behind some form of "load balancer"-like system at the network/io layer? Are self updating processes really the right abstraction? Seems like it kinda flips reliable build/deploy processes on their head a bit.

ConnorLeet · 4 years ago

Sounds like Erlang from what I’ve heard about it

ConnorLeet commented on Speeding up sort performance in Postgres 15 citusdata.com/blog/2022/0... · Posted by u/todsacerdoti

fuy · 4 years ago

Agree with you - would love to hear some of the core PG devs to pay attention and discuss this work.

ConnorLeet · 4 years ago

I think that this repo was created by a core PG dev.

https://github.com/orioledb/orioledb/commits?author=akorotko...

https://github.com/akorotkov

ConnorLeet commented on I Trained My TikTok metastable.org/2022/05/ho... · Posted by u/pbw

pbw · 4 years ago

> Bruh, get real. TikTok is filled with women complaining about dating. Why not just admit what is staring you in the face?

I’ve never see a video with a woman complaining about dating on TikTok. In years of use.

I’m not saying you are not seeing them, just that I have not seen one.

ConnorLeet · 4 years ago

Plenty of guys complaining about dating on TikTok too. It’s an absolutely massive platform and there’s videos on just about anything especially interpersonal relationships (coach industry)

ConnorLeet commented on Monorepos done right felixmulder.com/writing/2... · Posted by u/fixel

stadium · 4 years ago

> With regard to technical choices - consider that some languages & ecosystems provide a lot more "batteries included" than others

It sounds like you are happy with the language and stack, could you share what your team is running?

ConnorLeet · 4 years ago

.NET

ConnorLeet commented on Launch HN: Drifting in Space (YC W22) – A server process for every user driftingin.space/... · Posted by u/paulgb

ConnorLeet · 4 years ago

Do you have any resources to point me towards that elaborate on the benefits of a process-per-tenant/user for performance?

I work on a data-intensive app that fits the use-case you describe but I'm confused about the benefits for performance. (can certainly see how the code would end up nice/simpler) Is this mostly applicable to certain stacks?

ConnorLeet commented on Embeddable, replicated and fault tolerant SQL engine based on Sqlite github.com/canonical/dqli... · Posted by u/KingOfCoders

Labo333 · 4 years ago

What I found to be the biggest problem with SQLite is concurrent write operations. WAL helps for concurrent read but not for concurrent write.

On a moderate use case (< 20 write operations per s) I kept getting timeouts so I first devised a quick fix system using RQ jobs passing writes to a single process and migrated to postgres as fast as I could.

Does this software help with concurrent write operations?

ConnorLeet · 4 years ago

SQLite does have a branch that solves the concurrent write issue - not sure if this dqlite uses it https://sqlite.org/src/doc/754ad35c/README-server-edition.ht...

u/ConnorLeet

KarmaCake day34December 11, 2016View Original