How are you actually sending messages to the SMSC? If you are directly connected - IE using SMPP or UCP then I would imagine that there is a bottle neck at the SMSC. Large SMSC systems in the US typically deliver upto 1000 sm/s with larger systems delivering 2000+ sm/s - From the throughput you require I can see this could be a problem. I can imagine the carrier would not be happy for your application to dominate the SMSC and may impose throttling on your application.
What have you agreed with the carrier ragarding your connection. With a high volume application it is important to verify the network bandwidth available and round trip delays. Also, verify the the windowing parameters for the SMPP/UCP connection and the maximum number of connections you are allowed to make. Are you connecting to a multi-node SMSC? Then make separate connections to each node. Peter. phil wrote: > > Quite true and this lack of clarity was a mistake on my part. Requests > > from users do not really become a significant part of this equation > > because, as described above, once a user subscribes the onus is upon us > > to generate messages throughout a given period determined by the number > > of updates a user has subscribed to receive. > > > > > So you are trying to SEND a million times several packets every > 5 minutes? > No way Python is the bottleneck in that volume. > I have a POS app in Python that handles 10,000 packets > per SECOND including a MySQL lookup. > You have a bottleneck, but its not Python. -- http://mail.python.org/mailman/listinfo/python-list
