Reduce the clutter in notifications

[jamie]

would be great if there were a reduction in the amount and size of notifications that get pushed to the user.

I am finding that due to the current state all of my users simply ignore them and i can't blame them as they are too many of them and they have too much detail in them if they could be combined down so that multiable changes to a record are just a single notification, that they are smaller in genral and there are just less of them i think my users might start paying attention to them

its a great feature, but needs refining

[jacao]

We had over 1 million notifications stored in the table, which was significantly impacting server performance. After investigation and additional testing, we gained a better understanding of how this mechanism works.

We identified two necessary actions:

1) Adjust the global configuration, for example:

• Reduce bell notification retention from 30 days (default) to 14 days.
• Change bell status refresh interval from 10 seconds (default) to 1800 seconds.

With these changes, CPU usage (24 cores) dropped from approximately 60% to 1.5%.

2) Disable in-app notifications (email notifications are sufficient).

This reduces the notifications table growth by approximately 80,000 records per day (100 users × 800 emails).

The conclusion is that in-app notifications should be enabled only when truly necessary and properly configured. Currently, users see only selected information from followed records.

Regards! Jacek

[jamie]

wow!!!! yeah you can relate to why no one is looking at them. There's just too much clutter, it's a great idea but needs polishing up, maybe it should be a "turn it on" rather than a "turn it off" situation