04-19-2023, 08:09 PM
(This post was last modified: 04-20-2023, 08:34 PM by Alexandre Machado.)
From the start:
1- ok
2- 10 sessions is very little even if they are heavy users. 2000 sessions would be "a lot", although I had 3000 running on an Indy server.
3- Check the exceptions that the logger is saving
4- Please check the service process and see if it is still consuming CPU
5- ok
6- Direct connection is fine. Connection pool here would be an overkill
7- You can leave the memory leak check to a second moment
As a test, I would replace the memory manager and use FastMM4 just to see if it makes any difference. It may fix the problem or it can make it worse. I would use the one the comes with IntraWeb (v 4.992 4.991) because it has been fine tuned for IntraWeb/multi-threaded apps. It is rock solid.
1- ok
2- 10 sessions is very little even if they are heavy users. 2000 sessions would be "a lot", although I had 3000 running on an Indy server.
3- Check the exceptions that the logger is saving
4- Please check the service process and see if it is still consuming CPU
5- ok
6- Direct connection is fine. Connection pool here would be an overkill
7- You can leave the memory leak check to a second moment
As a test, I would replace the memory manager and use FastMM4 just to see if it makes any difference. It may fix the problem or it can make it worse. I would use the one the comes with IntraWeb (v 4.992 4.991) because it has been fine tuned for IntraWeb/multi-threaded apps. It is rock solid.