Dating Website Support Forum - Webscribble

I was wondering if anyone knows how many emails per second the Matchfinder is sending? Let's assume that it is set to send matches once a week and when it starts sending there are 2000 emails in the queue. Is there a way to control how many emails are sent per second?

Thanks

The matchfinder email does not have a built in delay on outgoing emails per second

also the way the matchfinder runs is it loads the matchfinder when a user logs in and the last run is within the time specified

this causes the browser to freeze up for this member who logs in at this point until the emails are sent.

the code to the matchfinder could be set to only send out so many mails per second

I would also recommend if you go this route that you modify the code so it is run as a cron job rather then within the webscribble script because this will cause the browser to freeze up to members who log in when the matchfinder is do to run.

tell me what your server limits are and also what type of server you are running on.

you do need some programming done to get your expected results.

Paul

Hi Paul,

Thanks for your reply.
There are a lot of things in your explanation that I don't understand.

1. Are you saying that the Matchfinder loads EVERY TIME, ANY USER logs in? That means that if I have 100 people login every day, then the Matchfinder will be loaded 100 times?
2. What do you mean under 'matchfinder is loading" exactly? I thought that the Matchfinder is running only when a new member registers to the site, and sets a record in the database (dt_queued). After that, based on these records, it is sending emails at the preset interval (daily, weekly .. etc).
3. I completely did not understand the browser freezing part. I've never noticed my browser to freeze when I log in.
4. You said that

The matchfinder email does not have a built in delay on outgoing emails per second

, but after that you say

the code to the matchfinder could be set to only send out so many mails per second

. Does that mean that it can be set, but it needs programming?
5. I did not understand the cron job part either. I guess I am not very familiar with how it works.
6. I am running on an Apache server. That's all I know. What do you mean under server limits?

Sorry for the many questions.

Thanks

Every time a new user signs up they are entered into the matchfinder dt_queued if they have matches

everytime the page index.php is loaded

this happens

require "engine/scheduler.php";

the schedule.php then

include "matchfinder.php";

the matchfinder script checks to see if the last run was longer than the setting (one week for example)

if the matchfinder has not run in the set time it will run sending out all the matches in the dt_que

if you happen to be the person loading the page when this happens this is when it will lock the browser

it will only happen to one user per matchfinder run (once a week for example)

also I asked about the server setting because... it sounded to me like you had some restriction on maximum outgoing mail per second?

why else would you need to modify this?

setting up as a cron job could run the matchfinder automaticly once a week without being loaded when someone visits index.php

yes the code would need to be modified to change the outgoing emails per second and would also need to be modified to be run as a cron job rather than being called by the script index.php

hope that cleared things up for you let me know

Paul