6194: Stats processing uses too much memory - Composr CMS feature tracker

ID	Project	Category	View Status	Date Submitted	Last Update

6194	Composr	stats	public	2025-04-08 01:33	2025-04-08 01:44

Reporter	PDStig	Assigned To
Priority	normal	Severity	minor
Status	new	Resolution	open

Summary	6194: Stats processing uses too much memory
Description	Stats pre-processing can easily eat up too much PHP memory (e.g. the events hook) since buckets are stored by month, and the entire months of every bucket are loaded in. Instead, I think buckets should be stored by day. It will be much easier to process without running into memory issues. * Make stats pre-processing loop by each day when a range of start / end time extends over multiple days (it shouldn't though because of the updated Cron!). * Only load bucket data for the specific day we are processing on that iteration; empty the array of bucket data after each iteration (and updating the database) to conserve memory. * Ensure nothing is modifying stats outside of the designated day; if they are, modify so they don't.
Additional Information	High priority; this affects composr.app and thus needs fixed ASAP.
Tags	Roadmap: v11
Attach Tags	(Separate by ",")

Time estimation (hours)
Sponsorship open

Date Added	Member	Amount Sponsored
2025-04-08 01:44:	PDStig	100 points

View Status	Private (for security issues or disclosing of private information; if you submit as a guest, you will not be able to see your submission)
Note
Upload Files Maximum size: 32,768 KiB	Attach files by dragging & dropping, selecting or pasting them.
You are not logged in	You are not logged in. This means you will not get any e-mail notifications. And if you reply, we will not know for sure you are the original poster of the issue.

Date Modified	Username	Field	Change
2025-04-08 01:34	PDStig	Tag Attached: Roadmap: v11
2025-04-08 01:44	PDStig	Sponsorship Total	0 => 100