Timeline for Strategy for Postgres updates with very high write load, but low consistency requirements
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17 at 9:48 | answer | added | bobflux | timeline score: 0 | |
| Feb 17 at 6:30 | comment | added | Luke Hutchison | @bobflux basically the issue here is that whatever the QPS is for obtaining query results consisting of lists of thumbnails, the write factor is multiplied by that number. I don't have actual numbers, but let's say we have 100 users querying the database per second on average, and each one fetches a result set consisting of 200 thumbnails. Then the total writes per second needs to scale to 100 * 200 / sec. This will get out of hand quickly. | |
| Feb 10 at 20:54 | comment | added | bobflux | How many thumbnail views per second do you expect? | |
| Feb 8 at 19:43 | comment | added | Laurenz Albe |
Why should that be horrendous? If you set a low enough fillfactor on the table and don't index the view count, these could be efficient HOT updates.
|
|
| Feb 8 at 19:19 | history | asked | Luke Hutchison | CC BY-SA 4.0 |