Configuring the Load Balancer (Windows)
The Informer Load Balancer (available in 5.0.13 and later) splits Informer into separate processes for its core components, which improves performance under larger request or data volumes. It is also the supported way to use HTTPS with Informer.
The processes are:
- Queries: handles all database query executions.
- API: the main web server component, handling all UI requests.
- Load-Balancer: acts as a proxy server and is the main entry point for all requests.
- Scheduler (optional): handles all schedule executions.
Each process can have as many threads and as much memory as needed.
Prerequisites
Run the commands in this article from the Informer installation directory (for example, C:\Entrinsik\Informer5) in an elevated PowerShell window. On Linux native installations, run them at a command prompt, using sudo or root as your system requires.
You need Informer CLI 1.0.4 or higher to configure the Load Balancer. Check your version with:
informer --version
If you need to upgrade the CLI, see Upgrading Informer (Windows).
Configure the Load Balancer
-
Stop the Informer service, then run:
informer load-balanceFor each process you are prompted for the number of threads and the port. Press ENTER to accept the defaults shown. You can edit the configuration later to adjust threads or ports.
-
Edit
config.jsonand verify that theurlentries under the load-balancer rules point tolocalhost, the server's hostname, or the appropriate server if Informer runs across multiple servers. For example:"url": "http://localhost:3002" -
Start Informer.
Verify the Load Balancer is running with:
pm2 monit
You should see separate processes for the API, query, and scheduler, plus the reverse-proxy service, which is the load balancer itself.
To change the number of threads later, edit service.config.json and modify the instances (threads) entry. To change ports, adjust the args entry for http. Restart Informer to apply the changes.
To serve Informer over HTTPS, see Configuring HTTPS (Windows).