Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Mozilla-based browsers become unresponsive during capacity planning calculations

Mozilla-based browsers become unresponsive during capacity planning calculations

Table of contents


The default number of persistent connections per server for Mozilla-based browsers is less than the number of opened connections during capacity planning.


Increase the maximum number of persistent connections allowed per server. For more information about network configuration in Mozilla, view the Mozilla article on About: config Network entries.


  1. Open a browser window.
  2. Enter About:config in the address bar.
  3. Click I'll be careful, I promise when prompted.
  4. Search for network.http.max-persistent-connections-per-server.
  5. Double-click network.http.max-persistent-connections-per-server.
  6. Enter 30 in the popup.
  7. Click OK.
  8. If you use a proxy to connect to your Virtualization Manager instance, increase the value for the network.http.max-persistent-connections-per-proxy entry as well.


Note:  While SolarWinds recommends 30 persistent connections per server to run capacity planning, this number may increase, especially if you use capacity planning widgets. If you notice slower response times and increasing the number of persistent connections previously improved performance, increase the maximum number of persistent connections again. Valid values are between 1 and 255.

Last modified