Restart application pool

You can restart your Windows Application Pool under the “Website” section in our control panel.

¶Why would you restart an Application Pool?

• Removal of hung processes
  Over time, processes in a pool can become hung or enter an unstable state due to memory leaks or unforeseen errors. A restart clears the current process and starts a new one, which often resolves such issues without you needing to restart the entire web server.

• Release of resources
  If an application has used a large amount of RAM or CPU for an extended period, a restart will free those resources, giving other sites on the server more capacity.

¶What happens when you restart the pool?

1. All active sessions are terminated – users who currently have an active connection to the website may experience a brief interruption.
2. The process is closed and a new one started – the .NET runtime reloads the configuration, and any memory leaks are eliminated.
3. The website's response may be slightly slower in the first few seconds – because the necessary assemblies and resources need to be loaded again.

After a few seconds, your web application will be ready again with the new settings or a fresh process. How often you should do this depends on your application's nature – in most cases a restart is only required for configuration changes or identified issues.