Viewing profile — pgaddict
pgaddict
HN member- Joined
- Thu, Mar 05, 2015, 8:50 PM UTC
- HN karma
- 1,111
- Public activity
- 380 items
- HN profile
- View on Hacker News ↗
About pgaddict
https://github.com/tvondra/
Recent public activity
-
comment
Comment #48356041
I really wish they clearly documented the parameters used by each of the databases (or are we expected to dig those out of the .rs sources somehow?), and actual versions used (sayi…
-
comment
Comment #48167581
Interesting paper. I only started reading / digesting it, but: - I'm not sure how to interpret the Figure 1. It says "Flash writes (KB) per page", but it doesn't really say which p…
-
comment
Comment #47648919
So why does it happen only with hugepages? Is the extra overhead / TLB pressure enough to trigger the issue in some way? Of is it because the regular pages get swapped out (which h…
-
comment
Comment #47231054
True. Unfortunately it's what index scans in Postgres do right now - it's the last "major" scan type not supporting some sort of prefetch (posix_fadvise or AIO). We're working on i…
-
comment
Comment #47216754
To the best of my knowledge, yes. Unfortunately the details of how it was calculated in ~2000 seem to be lost, but the person who did that described he did it like this. It's possi…
-
comment
Comment #47216671
Damn, I copied the wrong command. I wanted to copy this one: fio --filename=/dev/md127 --direct=1 --rw=randread --bs=8k --ioengine=io_uring --iodepth=1 --runtime=120 --numjobs=1 --…
-
comment
Comment #47211236
Good idea. It's an interesting historical question - when we picked 4.0 as the default ~25 years ago, how close was is to the calculated value? I was asking that myself. Unfortunat…
-
comment
Comment #47209955
Good point, I should have included that (the linked pgsql-hackers thread have some of this information, at least). I've observed exactly this behavior on a wide range of hardware /…
-
comment
Comment #47209797
There probably is some additional inefficiency when reading pages randomly (compared to sequential reads), but most of the difference is at the storage level. That is, SSDs can han…
-
comment
Comment #46139202
AFAIK these two joins are exactly the same once you get past the parsing. It's just a different way to write an inner join. It's translated into the same AST and so there's no diff…
-
comment
Comment #46136171
That is part of the key idea, yes. It's more elaborate, because it can split the aggregate - it can do part of it before the join, and finalize it after the join. Similarly to what…
-
comment
Comment #46135772
It's not about not knowing about an optimization. The challenge is to know when to apply it, so that it does not cause regressions for cases that can't benefit from it. It may be l…
-
comment
Comment #45715399
IMHO the whole point of Qubes is that it does not do the compartmentalization at the level of individual applications, but groups of applications. Otherwise you'd need to very clea…
-
comment
Comment #45425207
I'm not sure what exactly you mean by "thread" here. Postgres is not thread-based - there are people working on that, but for now it's all processes. Some of these limitations are …
-
comment
Comment #45421332
I believe there are reasons why e.g. io_uring could be inherently slower in some cases, and I tried to point some of those out. With io_uring everything happens in the backend proc…
-
comment
Comment #45421273
Debian 12/13, with kernel 6.15. Sorry, should have mentioned that in the blog post.
-
comment
Comment #45413837
> Right now async IO is used for sequential scans and bitmap scans, not for index scans. My initial guess would be that it mostly helps for complex queries (that use multiple index…
-
comment
Comment #45413674
I did a lot of tests comparing the io_method choices, and I'm yet to see a realistic query where it makes a significant difference of more than a couple percent (in either directio…
-
comment
Comment #44902561
The funny thing is the local communist newspaper "Red Truth" (as if there were non-communist ones, ...) published a review of LOTR in 1977, in which they pretty much took the side …
-
comment
Comment #44625594
The toaster mention reminded me of this: https://www.youtube.com/watch?v=LRq_SAuQDec This is how "talking to AI" feels like for anything mildly complex.
-
comment
Comment #44036409
I've been involved in a couple of those cases, where a large company ran into an issue, and chose to solve it by migrating to something else. And while the issues certainly exist (…
-
comment
Comment #42685109
I only noticed the jerky scrolling on pages with a lot of images, particularly hires + CSS effects (blur etc.). Everything else feels OK to me (I'm sure it could be smoother, but i…
-
comment
Comment #42685089
Thanks for the clarification.
-
comment
Comment #42684070
I occasionally see stutters too, even with Full HD video. Or more precisely, mplayer complained about slowness and having to drop frames. It often helped to actually give the VM mo…
-
comment
Comment #42683562
Not sure what "mpv" means in this context, but this reminds me the one actual pet peeve I have with Qubes - video/audio calls just don't work for me. It either doesn't work or the …