ServiceNow instance scalability

[soujanyanaganur]

I am trying to understand the scalability or limit in terms of number of users , applications build or integrations that can be set up on a single instance of ServiceNow production environment before we see performance degradation

[dravvyramlochun]

Hello   Soujanya

What every ServiceNow production instance gets:

• Two UI Nodes (all figures below are per node)
• 2GB RAM for each node
• Sixteen User semaphores available on each node (total of 32 concurrent transactions, or 32 people hitting the "Submit" button all at the exact same moment)
• Eight additional integration / SOAP semaphores (per node, total of 16), to ensure that user-land transactions are not impacted by integration and ODBC traffic.
• Eight background schedulers for (16 total) email processing, scheduled jobs, workflow timers, Discovery, etc.
• Thirty-two DB connections (64 total)

The default setup will handle probably 8k+ process (IT) users and 200,000+ end users.

However you can refer to below wiki link in case of any issues with the slow performance of the instance.

http://wiki.servicenow.com/index.php?title=Troubleshooting_Performance

Reference:

You can check a similar post on our community: Instance Performance   where valor   gave a good explanation that I posted above

Thanks,

Dravvy

Please Hit like, Helpful or Correct depending on the impact of the response

[Valor1]

This depends on so many things.

ServiceNow has been very responsive to use in terms of performance issues. The largest SN customers have along the lines of 20,000 fulfillers, 50+ integrations and 500k+ end users, with dozens of custom apps.

The primary source of performance issues come from developers doing dumb things (nested / synchronous ajax calls, etc.).. I'd say you'd more than likely be fine when managed correctly 🙂