Jeff Moden wrote:
If you've not had scale issues, then why all the business about limiting notations and shutting down notifications on old posts?
Perhaps a verbiage issue. Scale, to me, is concurrent users and handling a load there. We've not had that.
We have had a session overload with the processing of the notifications. Given the data model, which is poor in WP and isn't designed well for large filtering, the subscriptions were an issue. That is somewhat scale, but it isn't about writing better code, at least not within the design of the WP data model. It's about reducing the load, or about redesigning how the notification system works. In that case, we would be forking the forum code, which makes upgrades an issue.
We could submit a PR to the software developer, but since an improvement to handle a much larger level of notifications would be a data model change, moving away from how WP architects things, philosophically, I doubt it would be accepted.
As it is, my push is to abandon the WP model in places where we are building our own software in the name of being more efficient with computing resources and working with larger scales of things, but that's few places. Most of the time you are building something that you expect to work with singletons, or a session, in which case the silly JSON-stuff-many-things-into-a-field model works well.
It's a No-SQL/document DB kind of model for WP, which is highly scalable (concurrently) for singletons, less efficient for space usage, poor for data dupe and multi-row operations, but well understood by a class of developers working in that architecture.