I'm afraid I don’t have control over the mail server but I could talk to the
guy who does and see what he thinks. The person who coded this originally
was also over the mail server (and web servers) so maybe the new guy has
some ideas he can share in that department

After reading your post however, I think you missed one part of my logic. I
wasn’t planning on grabbing the top x, sending, flagging, then starting
over. After sending the TOP X number of emails... that process is basically
over and done with. A minute or 2 later, the same process will happen again
and grab the next TOP X emails.

That will most definitely be lighter on everything and everyone (except me
in the code department heh) unless I'm missing something else.

O'Hare must have an 8 hour minimum layover rule lol I had to weight darn
near 8 hours last time I was there. I'll try and keep you occupied for a bit
longer... no, no it's the least I can do to come up with questions for you.
Think nothing of it ;-p

..:.:.:.:.:.:.:.:.:.:.:.:.
Bobby Hartsfield
http://acoderslife.com

 

 


-----Original Message-----
From: Matt Robertson [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 03, 2006 12:56 PM
To: CF-Talk
Subject: Re: mass emailing from CF

I think you are going to have trouble with your Top X Items idea.

I try to shy away from batching mail in chunks like that.  Its just
not scaleable.  Either that or it has a fatal flaw hiding inside that
is just as bad as whatever your curent problem is.

In this case I think you have both.  Consider the fact that CF will
happily Select Top X, shoot out X emails, mark X db records and loop
around and do it again.  Sounds great.  Except CF will do it at speeds
that no doubt FAR exceed the capacity of your presently-hobbled
system.  I'd bet you aren't going to accomplish a thing with it
as-described.

So to solve that poblem you say to youself "I will slow it down
programmatically".  The olde tyme way was with a CFLoop inside your
mail loop set to run for X iterations where running those iterations
where those iterations take up some real time.  This has the side
effect of eating up processor cycles like a Tyrannosaur crashing the
Brontosaurus Family Reunion and also tying up a thread while the
brontosaurs are mowed down.

To which you can say "Aha... I have CFMX Version [whatever] so I can
call a java sleep method.  This is great news to the brontosaurs'
social calendar but still sucks down a thread for ever and ever.

.....Yes I know I am blabbing but I am in the middle of an 8 hr layover
at O'Hare Int'l Airport and am bored...

Why not look at your mail server?  Forget about CF for the moment.
Seems like the mail server is the problem.  Can you install, for
example, iMS?  There is a cheap version, and a free one too.  Run it
off a nonstandard port if you have port 25 already taken.

-- 
[EMAIL PROTECTED]
Janitor, MSB Web Systems
mysecretbase.com



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:251910
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to