Domain availability in store fronts
Configuring domainreg server for best performance
When performing domain availability check on any storefront for each TLD configured on Domain Registration server one process will be spawned.
Each process will require about 80 - 100 MB of RAM and dedicated CPU processing power.
In general Domain Registration server itself requires as little as 512 MB RAM to be operational. However, each domain extension availability check will require additional 80 - 100 MB of RAM.
In case Domain Registration server runs out of memory your end customer will see endless turning circle next to domain extensions that do not have sufficient memory to perform domain availability check.
If you want to offer great number of domain name extensions to your end customers on storefront, you will need to configure domain reg in smart way to handle this load.
Best approach is to bundle multiple domain extensions under one process which would be done like this in the configuration file (on DomainReg in /etc/domainreg.conf):
<tld> name = ac name = ae name = aero name = ag name = info registry_type = openprovider dri_timeout = 60 dri_remote_url = https://epp.cte.openprovider.eu/ dri_username = *********** dri_password = ******** dri_driver = Openprovider global_contact_authinfo = contact_id_generated_by_registry = 1 transfer_include_contacts = 1 periodic_registry_plugin_task = 0 initial_years = 1 domain_create_no_authinfo = 1 <connection> process_name = .ac.ae.aero.ag.info OP registration ratelimit = 0 handles interactive handles registration handles renewal </connection> </tld>
In the above configuration we are bundling five extensions under one process. Checking domain availability will take one process (up to 100 MB) for all five domain name extensions.
For example, of you would offer 100 domain name extensions, you can do following calculation / configuration:
|# of extensions per process||# processes||# RAM per process||Total RAM required|
|1||100||100 MB||10 GB|
|2||50||100 MB||5 GB|
|5||20||100 MB||2 GB|
|10||10||100 MB||1 GB|
You can also utilize our default Nagios monitoring installation to monitor the performance and RAM utilization on the server.