Property V4:FAQ
Service Speed
- What kind of speeds can be expected from the Property Web Service?
The Property Web Service can process hundreds of thousands of records per hour. The exact throughput the service achieves varies due to many factors, so your actual results will differ.
Some major factors impacting speed include:
- The number of threads used for sending requests:
- The service will handle multiple requests from your application simultaneously, increasing overall throughput. We generally recommend up to 10 threads.
- Batching vs single-record requests:
- The service can process 100 records in a batch (POST request) faster than 100 single-record GET requests.
- The type of input provided to the service:
- Free-form addresses will process more slowly than parsed inputs (Address Lines, City + State or Postal).
- Melissa Address Key (MAK) inputs will process relatively quickly since the MAK is a globally unique identifier.
- The quality of the input data provided to the service:
- If data is poor or malformed, Melissa will attempt to correct it. This will reduce the processing speed.
- The number of output columns selected:
- Requesting more response columns means more time querying our databases and larger payloads. More columns requested will result in slower responses.
With these variations in mind, you can expect the following approximate throughput rates:
| Endpoint | Throughput (records / hour) |
|---|---|
| LookupProperty | 300,000 - 1,250,000 |
| LookupDeeds | 250,000 - 500,000 |
| LookupHomesByOwner | 250,000 - 500,000 |