High-volume transactions and performance

Make sure you set up high-volume transactions on the PPSR correctly; otherwise you risk performance issues that can result in more charges and delays.

On this page

Make sure you set up high-volume transactions on the PPSR correctly; otherwise you risk performance issues that can result in more charges and delays. High-volume transactions include generating B2G messages, and search certificate requests and generation.

B2G activity trends

The bulk of transactions on the PPSR occur between 8 am and 6 pm, Monday to Friday. There is a slight dip in the transaction rate over the lunch period.

Schedule non-time-critical transactions after hours

If you are scheduling large batches of non-time-critical transactions and wish to limit the impact on the PPSR:

  • schedule transactions between 7 pm and 1 am
  • limit the number of requests in the batch to 1,000 requests/hour during business hours (8 am to 6 pm weekdays) and 5,000 requests/hour outside business hours
  • spread the requests over the hour (e.g. limit the number of threads making the requests).

B2G mailbox polling

Your B2G mailbox operates in the same way as email. More than 80 per cent of B2G messages coming to your B2G mailbox are expected messages and called RetrieveMessageRequestMessage.

When setting up your B2G mailbox polling, you need to schedule the following:

  • One message every 10 seconds for expected messages.
  • One message per minute for non-expected messages.

Generating search certificates

Search certificates are generated asynchronously with a request for a certificate search returning a search certificate number, and then the search certificate is queued for production.

Null search certificate

When the search certificate is generated, the search certificate’s PDF version is returned in the response message. If the search certificate is not ready, then a valid response is returned with a null search certificate field.

B2G client can continue sending new retrieve search certificate request messages until the search certificate is returned. If you use the same request message ID, the null search certificate response will be returned even if the search certificate has been generated.

Search certificate backlog

A search certificate is normally generated in less than 10 seconds. When there is a large backlog of search certificates in the queue, a certificate may take five minutes or longer to generate. If the delay is due to a PPSR problem, your certificates will be generated once the problem is resolved, in the order in which you requested them.

Recommendations for search certificate issues

Do not generate a new search certificate

If there is a delay in the generation of a search certificate, you should not request a new search certificate. This will only add to the queue and cause further delay.

Use your search certificate number to retrieve your search certificate

When you have requested a search certificate, you will receive a search certificate number, continue to retrieve that search certificate number rather than ask for another one. If you are requesting a large search certificate, it may take longer than 30 seconds to generate.

Request to retrieve search certificates in a timeframe

Send requests to retrieve search certificates using the timeframe – 1s, 3s, 5s, 10s, 1 min, 5 min, 20 min, 30 min, then every hour.

Was this information helpful?

We welcome your feedback to help us improve our website.
Unfortunately we are unable to respond to individual comments or suggestions.

For enquiries see the options available in our contact us section.