4 ms·
This paper is a tour de force. Well worth the read. Two things I wonder about: 1. Is the extra overhead of the fast path worth incurring on every call for mos
by yanowitz 12y ago
This paper is a tour de force. Well worth the read.
Two things I wonder about:
1. Is the extra overhead of the fast path worth incurring on every call for most use cases or should you only stall with a Postgres system?
2. What were the false starts in his analysis? How did he bail from them? What are the insurmountable bottlenecks?
- toast0 12y agoI haven't looked at the patches, but it seems unlikely that the checks for the fast path will add significant overhead to calls that aren't on the fast path. The fast path work should apply to other programs that use shared memory in the same fashion: large shared memory allocations, without a backing store, accessed by many processes across many processors. The lock reduction work in the buffer cache and page queues should apply more generally.