BUG - Delayed profile save during cupid mail queue

Hi, 

When a user has a lot of matches and cupid notification is enabled, it can take a very long time for that user to save their profile. This is because dolphin is queuing up the match emails to send. This queue processing should be sent to the cron process and not hold up a user's browsing experience. It took over 1.5 minutes to save a profile that in turn queued 16k emails.

Thanks

Can this get logged?

bump... 

bump...

:(

Emails are queued and can't cause delays, delay (most probably) is caused by matches calculation. 

I would recommend to limit matches calculation per one run.

in inc/match.inc.php file:

$aProfiles = $oDb->getColumn("SELECT `ID` FROM `Profiles` WHERE `Status` = 'Active' AND `ID` != $iProfileId $sCondSort LIMIT 1000");

Theoretically, since the result is cached, next time it will process another set of members and so on, so it shouldn't stop on the first 1000 members.

I'll try that. Buy while the save was occuring, I was refreshing the mailq and I could see it increasing. Does calculation and queuing occur in tandem?

 Upon saving, if there are matches, then emails about matches are added to the mail queue.

this additional bit of code "LIMIT 1000" seems to stop most cupid mail now... Where a profile update once created 16k mails... it now only created 6-700...