Sorry if I'm wrong, but I have noticed a increase in database queries with each page load and just did some debugging and got a bit of a fright. lol
I see that membership plugin calls the database for bunches of members on each page load. (Either bunches or the entire list of members - not sure?)
It cycles through list of members checking start_current / expire_current / and whether to send the communication emails.
This is only one member out of the list...
SELECT user_id, meta_key, meta_value FROM plus_usermeta WHERE user_id IN (1059) SELECT * FROM plus_usermeta WHERE user_id = 1059 AND meta_key LIKE 'start_current_%' SELECT * FROM plus_m_communications WHERE periodstamp >= 0 AND active = 1 ORDER BY periodstamp ASC SELECT * FROM plus_usermeta WHERE user_id = 1059 AND meta_key LIKE 'expire_current_%' SELECT * FROM plus_m_communications WHERE periodstamp < 0 AND active = 1 ORDER BY periodstamp ASC
Wow, I'm only testing with a 50 or so, what would happen with a couple of thousand?
Please tell me it is because of my testing environment - lol.
This is on my home pc - using wampserver.
And if it isn't surely the start / expire should run only when individual user logs in. And communications should possibly run on some sort of cron? / or at least an option to deactivate it entirely.