[OPENIG-4753] Doc: Fix Standalone Performance Issue (OPENIG-4715) Created: 03/Jul/20 Updated: 07/Jul/20 Resolved: 07/Jul/20 |
|
| Status: | Resolved |
| Project: | Identity Gateway |
| Component/s: | Doc |
| Affects Version/s: | Not Applicable |
| Fix Version/s: | 7.0.0 |
| Type: | Task | Priority: | Blocker |
| Reporter: | Guillaume Sauthier | Assignee: | Joanne Henry |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | 7.0 - IG-X Foundations | ||||||||
| Sprint: | 2020.09 - IG / Microservices | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
The main required change will be to add that the ClientHandler (and ReverseProxyHandler) connections attribute, when used in Standalone, is not really the absolute maximum. In fact it is the maximum number of HTTP/1.1 connections to keep in the pool per Vert.x HTTP Client, and we have as many Vert.x HTTP Clients than gatewayUnits (in the admin.json). So, if you do have set gatewayUnits: 3, you can observe as much as 3 * connections concurrently to the protected application (if this handler is only used for contacting the protected app). |