Hi Ernesto, > Is this normal? Is there any way to speed this up? Or is this a bug?
That question is almost impossible to answer without knowing more about your server - how powerful it is, how busy it is, and most particularly, how fast its connection is the the BWW (Big Wide World tm) is. Not only that, but what about the sending server? How fast any one transaction is: i.e. Sending a message by SMTP from the sending MTA to the receiving MTA, depends on the following factors: - 1 How fast the sending MTA is. The more powerful the machine is, the more simultaneous streams of outgoing traffic it can handle simultaneously. This is dependent not only on the physical hardware, but also on the OS and the MTA software used. 2 How busy the sending MTA is. The most powerful machine will slow down if it's trying to process hundreds of simultaneous incoming and outgoing messages 3 How fast the sending MTA's connection is to the Internet. It doesn't help to have a powerful machine, if it's only connected on a 64 kbps leased line 4 How busy the connection to the Internet is. A 2 Mbps connection will soon be filled up by a busy MTA 5 How busy / how much spare capacity there is in the portions of the Internet between the sending MTA's connection to its upstream ISP and the receiving MTA's connection to its upstream ISP. There may be many hops involved here. Every packet is sent at the full speed of the link. Too many packets trying to fit through a slow link will overload it, with the result that a particular message will be slow. 6 - 9 All the same factors above for the receiving MTA, except that here both ASSP and your MTA apply. Remember, ASSP is (simply!) acting as a proxy between the sending MTA and the receiving MTA. Thus, if either ASSP or the receiving MTA is overloaded, both will have to slow down. Furthermore, ASSP is (except for the new beta version 2) a single threaded threaded process. That means that all incoming streams - and there can be many - are effectively handled by a single process. This makes no difference for a lightly loaded system, but if it's trying to process dozens of simultaneous messages, they are all handled by a single process, including virus scanning, etc. Thus, each one has to wait for the previous one to complete a stage of processing. In the case of my installation, I see many message that are processed at several 100 kbps, and others that seem to crawl as you describe. The difference is primarily due to the sending MTAs, not my installation. How many simultaneous messages do you allow? What about reducing this number? That will make each message happen faster, but will slow down overall delivery to a point where your ASSP/MTA combination may be better able to cope, thus "smoothing" delivery. Conversely, if delivery is delayed but machines & links are not overloaded, you should consider increasing this number. How many messages per day does your system process? Have you looked at a graph of your bandwidth consumption, and compared it to the available capacity? Have you looked at the CPU load of ASSP and your MTA on a graph? Have you looked at how many simultaneous processes are running on each machine? Are ASSP and your MTA running on the same machine? One tricky issue: If any portion of the link between the sending MTA and the receiving MTA has a reduced MTU, and this isn't correctly configured, larger messages will have many packet retransmissions, and may fail entirely. Even if configured correctly, packet fragmentation will result in effectively slow transmission. This is often a factor in poorly configured wireless networks. > I'm seeing several connections that have been connected for over 200 seconds. The data is still coming in as I can see the Bytes increasing. The thing is, the data is coming in sooo slowly. Are these slow processes timing out? If not, perhaps you don't need to worry. > Is this due to ASSP scanning the data or attachment (if there is any)? That can certainly be a factor. As you can see, there are many factors that could be affecting this. HTH. Kind regards, William Stucke. Ernesto Nieto wrote: > I'm running version 1.5.1.2 > and I'm looking at the SMTP Sessions screen. I'm seeing several connections > that have been connected for over 200 seconds. The data is still coming in > as I can see the Bytes increasing. The thing is, the data is coming in sooo > slowly. Is this due to ASSP scanning the data or attachment (if there is > any)? I do believe I've seen this before where a 19K attachment took over > 20 minutes to be received by ASSP. Is this normal? Is there any way to > speed this up? Or is this a bug? > Thanks > Ernesto > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Assp-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-user > > . > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
