It is important to keep in mind that the processing of information requires the use of computer memory and processor resources. Last Visit™ will process as many memberships as you allow without regard to system resources. In other words, if you have Last Visit™ set to process 100,000 members every 5 minutes, that is exactly what it will do, even if it kills your server in the process. Websites with small numbers of memberships do not have to worry about this as much as those with large numbers of memberships. If you set it to process 100,000 members, but your website only has 500 members, then 500 is all that will be processed each time.

Never allow Last Visit™ to run continuously. For example, if you have Last Visit™ set to process 300,000 members every 5 minutes, but it takes 5 minutes to complete the processing job, the processing will run virtually non-stop and your host will hate you.

Last Visit™ will not run more than one processing job at a time. This helps to ensure that the server is not bogged-down during processing.

Be reasonable when setting up Last Visit™. Allow Last Visit™ to process smaller portions of the information over a period of time rather than all of it at once.