Insights

Fast, Flexible and Efficient: Performance Upgrades are Coming to the New SMS/800 TFN Registry!

Jun 06, 2019

The finish line is near and the end in sight! As we edge closer to the full cutover for the SMS/800 Toll-Free Number (TFN) Registry from the current mainframe system to the new cloud-based system, there are a number of upcoming performance and timing changes that will provide higher throughput and reduced latency.

• For starters, users will find that the modernized SMS/800 TFN Registry is highly scalable and capable of processing more transactions at a much swifter pace than ever! 
• Responsible Organizations (Resp Orgs) will save valuable time when they leverage the new system’s ability to process requests concurrently as they arrive, thus making existing queues obsolete. 
• Performance improvements will be most apparent when activity is high – such as during the sparing hour. 

The following table shows you just how much the new system and API will increase speed and streamline transactions – specifically during the sparing hour – when the system is under its highest load. Web-Based Access (WBA) and Mechanized Graphical Interface (MGI) users will also benefit from the improved performance; however, they can expect an additional 50-100 milliseconds of latency over and above the below API metrics due to the use of adapters.

*Please note that timing observed by Somos testing is in seconds and does NOT account for latency related to network/internet speeds.

In addition to enhanced speeds, the SMS/800 TFN Registry will also implement new throttling limitations that will replace the existing Central Processing Unit (CPU) limit. The new throttling limit will be the same across all Resp Orgs to ensure fair and equitable access to the system.  

At the June 24, 2019 full cutover, Resp Orgs can expect the following:

• The SMS/800 TFN Registry will enforce a throttling limit of 5,000 transactions per minute, per Resp Org entity. If the throttling limit is reached, the system will stop processing any new requests for that entity with the excess transactions permitted to be processed the following minute.
• For User Interface (UI) and API users, when the throttling limit is reached, the system will stop processing any new requests and a throttling message will be returned.
• For MGI users, MGI requests go through an adapter to translate requests into an API call, and in order to maintain backward compatibility, will not receive a throttling message. If MGI requests reach the throttling limit, the SMS/800 TFN Registry will attempt to execute the request in the order it was received once the limit is reset.
• For WBA users, WBA requests similarly go through an adapter to translate requests into an API call, though WBA only supports synchronous (one at a time) requests. When WBA reaches the throttling limit, a system message is returned to the user.

See the new performance and timing changes in action when you join us on June 11, 2019 at 2:00 PM ET for a new webinar that includes a live walk-through. The webinar will feature an open Q&A session to help ensure that you are fully prepared for the cutover. Click here to register today!