Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

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

Mozilla-based browsers become unresponsive during capacity planning calculations

Table of contents

Overview

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

Resolution

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
04:11, 23 Jun 2016

Tags

Classifications

Public