[buddypress-trac] [BuddyPress Trac] #7534: Remove read notifications from the DB table after a specified time period
buddypress-trac
noreply at wordpress.org
Wed Aug 28 19:34:58 UTC 2024
#7534: Remove read notifications from the DB table after a specified time period
-------------------------------------------------+-------------------------
Reporter: r-a-y | Owner:
| espellcaste
Type: enhancement | Status: assigned
Priority: normal | Milestone: 15.0.0
Component: Performance | Version:
Severity: normal | Resolution:
Keywords: dev-feedback needs-unit-tests |
needs-refresh |
-------------------------------------------------+-------------------------
Comment (by johnjamesjacoby):
Maybe it will help to define ahat the reason is BuddyPress has this
goal/intention, and then make sure we are doing those things.
Here, we’ve explained what we want to do, but not really what results we
want to see to call it successful or a priority.
Do we think having fewer rows in this database will make it faster? If so,
how many rows makes it too slow, and what is “too slow” and what default
metrics do we consider reasonable, plus now we are introducing new options
to the Notifications component, and is that the best thing for all
installs?
Even though we can make safe assumptions, and even though we are acting
with good intentions of making things faster & better, we don’t know if
(as one example) maybe instead of permanently deleting rows we can add a
custom “pruned” status that omits those rows from the indexing, and gain
performance without losing data.
Does permanently deleting a notification unintentionally make anything
worse from the members perspective? Does it unintentionally lock the
database while those rows are deleted and the indexes are recalculated?
Does it create a situation where a member might get a Notification Email
that gets deleted by the time they get to click the link and read it? What
happens now if someone tries to view a deleted notification via email?
Or, can we routinely prune notifications from the members perspective
without permanently impacting other connected experiences? 🤔
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7534#comment:17>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list