Property V4:FAQ - Revision history

Admin at 23:35, 28 March 2024

2024-03-28T23:35:43Z

@@ Line 51: / Line 51: @@
 *If there are any quality issues identified with the updates from the county
 :Generally speaking, tax assessments may occur as frequently as twice-annually, or they may not even have a specific interval. Many counties only perform tax assessments when properties are sold, when there is a significant reduction in property value, or improvements are made (if reported by the owner) to the property.
 [[Category:FAQ]]
 [[Category:Personator Consumer]]

Admin at 00:07, 8 April 2022

2022-04-08T00:07:49Z

@@ Line 31: / Line 31: @@
 |LookupHomesByOwner||250,000 - 500,000
 |}
 [[Category:FAQ]]
 [[Category:Personator Consumer]]

Admin at 01:02, 19 February 2022

2022-02-19T01:02:01Z

Admin: Created page with "← Property V4 {{CustomTOC}} ==Service Speed== ;What kind of speeds can be expected from the Property Web Service? The Property Web Service can process hu..."

2022-02-19T00:59:33Z

Created page with "← Property V4 {{CustomTOC}} ==Service Speed== ;What kind of speeds can be expected from the Property Web Service? The Property Web Service can process hu..."

New page

[[Property V4|← Property V4]]
{{CustomTOC}}
==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:

{|class="alternate01" cellspacing="0"
!Endpoint!!Throughput (records / hour)
|-
|LookupProperty||300,000 - 1,250,000
|-
|LookupDeeds||250,000 - 500,000
|-
|LookupHomesByOwner||250,000 - 500,000
|}

[[Category:FAQ]]
[[Category:Personator Consumer]]

← Older revision		Revision as of 01:02, 19 February 2022
Line 8:		Line 8:
	Some major factors impacting speed include:		Some major factors impacting speed include:

	*The number of threads used for sending requests:		#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.		#*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:		#Batching vs single-record requests:
	**The service can process 100 records in a batch (POST request) faster than 100 single-record GET 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:		#The type of input provided to the service:
	**Free-form addresses will process more slowly than parsed inputs (Address Lines, City + State or Postal).		#*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.		#*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:		#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.		#*If data is poor or malformed, Melissa will attempt to correct it. This will reduce the processing speed.
	*The number of output columns selected:		#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.		#*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:		With these variations in mind, you can expect the following approximate throughput rates: