Re: Avoiding repeated snapshot computation
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: pgsql-hackers@postgresql.org
Cc: Pavan Deolasee <pavan.deolasee@gmail.com>
Date: 2011-11-26T20:42:12Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Slightly reorganize struct SnapshotData.
- 1fc3d18faa8f 9.2.0 cited
Attachments
- snapshotdata-one-cacheline.patch (text/x-patch) patch
Hi, On Saturday, November 26, 2011 04:52:50 PM Pavan Deolasee wrote: > I think now that we have reduced the run time of the function itself, > we should now try to reduce the number of times the function is > called. Robert proposed a way to reduce the number of calls per > transaction. I think we can go one more step further and reduce the > number for across the transactions. You could also try if it makes a difference reducing SnapshotData to one instead of two cachelines. The data itself fits into one without problems. Trivial patch attached. Generally I think we should check that for most of the more commonly used strutures, we have many with too much padding. Andres