Spot on, Raul Junco! I would only add - look for any "max count" bottleneck, which very often is your problem under load:
- Max concurrent DB connections settings.
- DB connection pooling settings.
- Max threads limit settings (web servers) - observe request queue being greater than 0.
- TCP stack issues (max outboind TCP connections), especially on Windows web hosting.
I've seen it many times - the server hosting the monolith has a lot of free resources, still the application is frozen! All these arw actually very easy to increase and fix temporarily the issue, to buy time for monoloth decomposition.
Greetings from a fresh subscriber (coming from linkedin) 🙂!
Spot on, Raul Junco! I would only add - look for any "max count" bottleneck, which very often is your problem under load:
- Max concurrent DB connections settings.
- DB connection pooling settings.
- Max threads limit settings (web servers) - observe request queue being greater than 0.
- TCP stack issues (max outboind TCP connections), especially on Windows web hosting.
I've seen it many times - the server hosting the monolith has a lot of free resources, still the application is frozen! All these arw actually very easy to increase and fix temporarily the issue, to buy time for monoloth decomposition.
Greetings from a fresh subscriber (coming from linkedin) 🙂!
Good one.
You can have plenty of CPU and memory and still freeze because one pool or thread cap is saturated.
Raising those limits often buys critical breathing room, as long as you do it intentionally and with monitoring.
And welcome, glad to have you here 🙌