24 Shared Registration System (SRS) Performance
|gTLD||Full Legal Name||E-mail suffix||Detail|
The heart of the shared registration system consists of a website for registrars and other parties that are connected to the registry, and the EPP service that administers domain, contact and host objects. The website of the registration system is allowed to query lists of domain, contact or host objects, but is not allowed to make object modifications. All modifications on the registry objects are done through the EPP service.
All services reside on redundant hardware, supported by both a hot standby and a cold standby facility on different physical locations. All data resides on storage solutions and is replicated automatically over the hot- and cold standby facilities. The hot standby is never more than a few minutes out of sync with the main facility. In case of a disaster on the main location, website and EPP services can switch to the hot standby facility within one hour. The cold standby data is replicated once a day.
All services have at least 2 instances running at different virtual machines. The load between the instances is handled by load balancers that will direct packets to the fastest-responding service.
When response times of the services drop below an acceptable level, new servers will be rolled out and load-balancers will be changed to include the new servers. The EPP servers are programmed to distribute load of requests over multiple instances of the servers.
Interoperability with other systems
The database of the registration system is queried on a read-only basis by the WHOIS service, and by the automated procedures that generate reporting to ICANN or other parties.
The EPP service is used by the website for all modifications of EPP objects. The website has direct access to the EPP database, but that is a read-only access for generating lists. The website is not allowed to directly modify EPP objects, only through the EPP service.
Registration System Performance
The following tests have been performed on the registry system via the EPP service. The tests were performed with a PHP program as a client and the java-written EPP service as server. This test is done on a single instance of the EPP service running at one single location.
50 concurrent connections: MIN,AVG,MAX are in milliseconds. Benchmark took 535 seconds to handle 150000 transactions. Average 269 transactions per second.
Type Min (msec) AVG (msec) MAX (msec) total 95th percentile (msec)
checkContact 1 22.7755 714 10000 65
checkDomain 9 34.8354 715 10000 83
checkHost 2 23.6579 705 10000 67
createContact 11 89.6172 1080 10002 201
createDomain 27 161.7708 1204 10001 350
createHost 11 83.2008 1076 10001 183
deleteContact 16 101.9805 1088 1995 228
deleteHost 11 82.4095 848 1966 178
infoContact 2 41.254 825 30000 111
infoDomain 12 44.3958 803 10000 116
infoHost 4 32.8313 1040 20000 92
login 21 48.5294 123 51 104
logout 5 15.2941 121 51 28
pollReq 5 111.8144 1325 10000 295
updateContact 16 101.6966 1076 10000 226
hello 14 40.9412 263 51 69
total 10.2 66.4042 849.5333 144067 186
runtime seconds: 535
The registry system logs all issued commands, together with specific command type information (info, create, modify, delete) and object information (domain, contact, host object). This enables us to create detailed reports on the performance of the registry service. If performance is drops over time, the software is prepared to distribute requests over multiple instances of the registry service.
The resource indentifiers used in this document are detailed in the text of question 46
Resourcing in the initial phase; This is for setup only, the functions already have been programmed and tested.
R.1 System engineer Infrastructure setup 2 days
R.7 Programmer Software setup 3 days
R.6 Project leader Project lead 2 days
R.8 Tester Website testing 1 day
R.11 Designer Website design 1 day
Resourcing for ongoing maintenance
R.2 Operations Engineer Maintenance of infrastructure 1 day ⁄ year
R.5 Support personnel Handles questions from registrars and registrants 100 days⁄year
R.6 Project manager Oversees changes to the system 2 days ⁄ year
R.7 Programmer Programming of changes 8 days ⁄ year
R.8 Tester Testing changes 2 days ⁄ year
R.9 Release manager Releasing software 2 days ⁄ year
T.5 Change board Approval of major changes to the websites As-needed basis
Similar gTLD applications: (0)
|gTLD||Full Legal Name||E-mail suffix||z||Detail|