|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Before assuming that the problem is w/ your iSeries, I'd check other things down the line. Seems like when MSF performance is complained about, the issue often ends up not being with MSF but with the network downstream. We send out 100's of e-mails everyday - many with attachments ranging from 1k to 10k - and the typical delivery time is under a minute (tried one just now and it was 20 seconds). We have a 720 w/ 768 main, with over 100 users. We've been using the QtmmSendMail API for a couple of years now with no complaints about performance. Dave -----Original Message----- From: Reeve Fritchman [mailto:reeve@ltl400.com] Sent: Monday, September 10, 2001 3:12 PM To: midrange-l@midrange.com Subject: RE: QTMMSENDMAIL performance Phil, thanks for your suggestions. This is the server of the future, all right :(...I guess decent e-mail performance is an unworthy component of e-business. Oh, I know...CFINT controls it to make sure e-mail is delivered promptly. I assume Lotus Notes uses the same API and I assume their performance is somewhat better. I guess I'll stop MSF and restart it and see if I can figure out what's up.... -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Phil Sent: Monday, September 10, 2001 3:51 PM To: midrange-l@midrange.com Subject: RE: QTMMSENDMAIL performance Reeve, MSF performance is a complaint often voiced. If you're sending only one e-mail address at a time to the API then you may want look at sending an array of e-mail addresses. This may speed things up if you're sending the same e-mail to 100's of recipients. If you're timing the mail delivery you probably should start counting when the e-mail hits your firewall. Then you'll be able to tell where the bottleneck is. Maybe your firewall can log when smtp mail passes through it? Phil > -----Original Message----- > From: midrange-l-admin@midrange.com > [mailto:midrange-l-admin@midrange.com]On Behalf Of Reeve Fritchman > Sent: Monday, September 10, 2001 3:14 PM > To: midrange-L@midrange.com > Subject: QTMMSENDMAIL performance > > > I hope this question doesn't require a book-length answer. > > My new 820 (V5R1, 1gb. Main, lotsa DASD) has a 128K fractional T1 to an > MCI/UUNet IP address through a NetScreen firewall. We have 7 > developers and > 4 support people on-line; our batch workload is light. So why > is a simple > QTMMSENDMAIL transaction so slow (up to 15 minutes) to reach its > destination? > > There are many factors outside the iBox which could be causing > the problem, > but sending e-mails between RoadRunner, AT&T WorldNet, and Qwest accounts > takes much less time. So the problem is in the iBox or with > MCI/UUNet (like > that would be a surprise!). > > *SHRPOOL1 is our batch subsystems; *SHRPOOL2 is HTTP and TCP tasks. No > QSYSOPR messages and we IMPL 2x/week. > > I'd appreciate any suggestions to improving MSF performance... > > 09/10/01 > 13:48:32 > % CPU used . . . . . . . : .1 System ASP . . . . . . . > : 111.6 > G > % DB capability . . . . : .0 % system ASP used . . . : > 25.1812 > Elapsed time . . . . . . : 00:00:01 Total aux stg . . . . . > : 111.6 > G > Jobs in system . . . . . : 1290 Current unprotect used . > : 1536 > M > % perm addresses . . . . : .007 Maximum unprotect . . . > : 1597 > M > % temp addresses . . . . : .012 > > Sys Pool Reserved Max > Paging > Pool Size M Size M Act Pool Subsystem Library > Option > 1 160.33 72.42 +++++ *MACHINE > *FIXED > 2 213.66 .28 61 *BASE *CALC > 3 128.00 .44 20 *SHRPOOL2 *CALC > 4 10.00 .00 1 *SPOOL *CALC > 5 256.00 .00 26 *INTERACT *CALC > 6 256.00 .00 10 *SHRPOOL1 *CALC > > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) > mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
