[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4758: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3893)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4760: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3893)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4761: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3893)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4762: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3893)
phplist forums • View topic - Throttled Sending Instead of Batches

Throttled Sending Instead of Batches

Solutions for other advanced phplisters

Postby drubarth » 7:56am, Wed 20 Jul, 2005

Darryl Rubarth

Web hosting and support for open-source solutions
drubarth
PL Master
 
Posts: 188
Joined: 10:14pm, Fri 17 Dec, 2004

Postby silverbytes » 2:36pm, Thu 21 Jul, 2005

silverbytes
PL Nut
 
Posts: 45
Joined: 4:13pm, Fri 18 Mar, 2005

Postby waznu » 9:24pm, Fri 22 Jul, 2005

waznu
phpLister
 
Posts: 14
Joined: 9:26pm, Tue 21 Jun, 2005

Postby jotazzu » 5:26pm, Fri 29 Jul, 2005

jotazzu
PL Master
 
Posts: 183
Joined: 6:31pm, Wed 13 Jul, 2005
Location: Hamburg, Germany

Postby drubarth » 6:52pm, Sat 30 Jul, 2005

Darryl Rubarth

Web hosting and support for open-source solutions
drubarth
PL Master
 
Posts: 188
Joined: 10:14pm, Fri 17 Dec, 2004

Postby jotazzu » 7:19pm, Sat 30 Jul, 2005

jotazzu
PL Master
 
Posts: 183
Joined: 6:31pm, Wed 13 Jul, 2005
Location: Hamburg, Germany

Postby drubarth » 7:50pm, Sat 30 Jul, 2005

Darryl Rubarth

Web hosting and support for open-source solutions
drubarth
PL Master
 
Posts: 188
Joined: 10:14pm, Fri 17 Dec, 2004

Postby jotazzu » 12:07am, Sun 31 Jul, 2005

I've my post published. There is also a separate post which explains the problem in detail.



This is a quite long topic. Hope you find some interesting things. It was hard work to put it all together.

Jochen
jotazzu
PL Master
 
Posts: 183
Joined: 6:31pm, Wed 13 Jul, 2005
Location: Hamburg, Germany

Re: Throttled Sending Instead of Batches

Postby orangechicken » 4:52pm, Thu 04 Aug, 2005

orangechicken
phpLister
 
Posts: 6
Joined: 4:38pm, Thu 04 Aug, 2005

Postby bumbum » 6:28pm, Fri 16 Sep, 2005

bumbum
phpLister
 
Posts: 6
Joined: 12:09am, Thu 25 Nov, 2004
Location: Dublin, Ireland

Postby jotazzu » 8:20pm, Fri 16 Sep, 2005

jotazzu
PL Master
 
Posts: 183
Joined: 6:31pm, Wed 13 Jul, 2005
Location: Hamburg, Germany

Postby SamIAM » 5:36pm, Fri 23 Sep, 2005

SamIAM
PL Nut
 
Posts: 22
Joined: 5:30pm, Fri 23 Sep, 2005
Location: Michigan

Postby jotazzu » 11:59pm, Fri 23 Sep, 2005

Hi,
PHPlist is able to handle such parallel invocations of processes to some extend. If a newly started process finds a running process it waits up for 20 seconds.
You will see messages like:
- A process for this page is already running and it was still alive xxx seconds ago
- Sleeping for 20 seconds, aborting will now quit

If still the previous process is running after 220s the new one finishes itself.
You will see a message like:
- We've been waiting too long, I guess the other script is still going ok

But when the previous process started more than 1200s ago and still is marked as running, the old one is killed without notice and the new one starts to process. This is the programming for v2.8.12 as you can find it at function getPageLock() in the file lib.php.

As you describe your scenario I assume that you are using throttling. The amount of 1000 emails you are sending in 5 hours is quite low. If your email is not bigger than 30kB any method which may be used with cron (PHP-cli, PHP-cgi, lynx, wget, GET, ...) should still be active after that time.

When the new cron job starts after 5 hours it will kill the previous job because the old one started more than 1200s ago. The new one takes over the processing of the queue. This is a completely new start and it continues to send the emails where the previous was stopped. If you added a new message meanwhile this is handled as if both messages are new. So there should be no difference to start both messages at the same time or to add the second later.

But don't use MAILQUEUE_BATCH_SIZE > 0 with your scenario. Only the first batch period will be executed before the process finishes.
jotazzu
PL Master
 
Posts: 183
Joined: 6:31pm, Wed 13 Jul, 2005
Location: Hamburg, Germany

Postby SamIAM » 3:24pm, Sat 24 Sep, 2005

Thanks for the great info.

I wonder, if i can change that 1200s number to make it much much larger, like 5 hours worth. Or maybe, i can make it where it will only start the new message send ONLY after the first one finished.

It takes me that long, becuase my host has a 200 emails/ hour.

Thanks again for the info.
SamIAM
PL Nut
 
Posts: 22
Joined: 5:30pm, Fri 23 Sep, 2005
Location: Michigan

Cli vs cgi mode

Postby robertp3 » 4:45pm, Sat 01 Oct, 2005

How can I determine which mode I am using when PHPlist is installed on a shared hosting service (in this case IpowerWeb).

I need to add the correct cron job to implement the throtte mod in topic below

http://www.phplist.com/forums/viewtopic.php?t=2142
robertp3
phpList newbie
 
Posts: 1
Joined: 4:38pm, Sat 01 Oct, 2005

PreviousNext

Return to Advanced Answers, Howtos, Tips & Tricks

Who is online

Users browsing this forum: No registered users and 0 guests

cron