4 ms·
I wouldn't characterize things as "falling over", except perhaps in cases of operator incompetence. There's certainly room for improvement — The Fine Article w
by rosser 9y ago
I wouldn't characterize things as "falling over", except perhaps in cases of operator incompetence.
There's certainly room for improvement — The Fine Article wouldn't exist otherwise — and backpressure might be worth exploring as a means of improving things. If that backpressure causes the system to slow down in a way that adversely affects customer or end-user interactions, however, it will often just be turned off, mooting it — or making things worse.
- hinkley 9y agoLike a lot of people, I was barely aware of VACUUMing before several high profile OLTP systems had unplanned outages because Postgres' requests per second dropped off dramatically and suddenly due to this arcane form of resource exhaustion. That's a performance cliff. I didn't mean it is hyperbole but as jargon. System hits a bottleneck, rate-of-change alters drastically/unmanageably.
- rosser 9y agoThat sounds like operator error to me. If you (the general "you") use a database in production without knowing what sorts of maintenance it requires, that's neither the database's nor its authors' fault. I guess you could argue the tool is somehow "flawed" for needing maintenance. I'd counter with the invitation to show me tools that don't.