Eclipse Community Forums: Eclipse Scout » Scout Application very Slow when 10+ Users are logged in

Help

Home

Home » Eclipse Projects » Eclipse Scout » Scout Application very Slow when 10+ Users are logged in

Show: Today's Messages :: Show Polls :: Message Navigator

Scout Application very Slow when 10+ Users are logged in [message #1829127]

Thu, 25 June 2020 14:43

Luis Nothvogel

Messages: 56
Registered: October 2019

Member

Hello,

We have got a problem with our Application. As soon as 10+ Users are logged in simultaneously from different machines the Application gets very very slow. We dont know where the problem is.

Example:
Sorting a table different takes around 10 seconds. And the table only has around 10 Rows. This applies for every other process in the application.

Is this a known issue? Did we do something wrong? Are there any config paramters we could adjust, to solve this?

Our setup:
Backend: 1x Windows Server with Tomcat (v.9)
Frontend: 1x Linux Server with Tomcat (v.9)
Scout: v10

Thank you for helping as always :)

Report message to a moderator

Re: Scout Application very Slow when 10+ Users are logged in [message #1829128 is a reply to message #1829127]

Thu, 25 June 2020 14:48

Arthur van Dorp

Messages: 48
Registered: October 2015

Member

Do you see any special CPU load, memory usage, disk i/o load or network congestion on the backend, frontend or database?

Report message to a moderator

Re: Scout Application very Slow when 10+ Users are logged in [message #1829131 is a reply to message #1829128]

Thu, 25 June 2020 14:55

Claudio Guglielmo

Messages: 256
Registered: March 2010

Senior Member

Please also check the currentThreadCount. Does it increase when more users connect or does it stay at a low level (e.g. 10?)

Do you deploy your app regularly using Tomcat deployer without restarting the Tomcat after a new deployment?

Report message to a moderator

Re: Scout Application very Slow when 10+ Users are logged in [message #1829132 is a reply to message #1829128]

Thu, 25 June 2020 15:26

Luis Nothvogel

Messages: 56
Registered: October 2019

Member

I didnt notice any spikes in any of that. But i will try a collect some data and i will get back to you with that

Report message to a moderator

Re: Scout Application very Slow when 10+ Users are logged in [message #1829133 is a reply to message #1829131]

Thu, 25 June 2020 15:31

Luis Nothvogel

Messages: 56
Registered: October 2019

Member

So i can only check the Thread count for the backend Server. Because i dont have direct acces to the Frontend server. But on the Backend i noticed that it starts with 10 Threads that are ready. As soon as I log in with a User 1 Thread is taken by 1 User. But as soon as i get to the starting number (10) it wont create anymore Threads. So maybe that is the problem? So as soon as 10+ Users are logged in all Threads are taken and it wont create more that these 10.

Do you know if that is the problem?

I only deploy the Frontend to through the Tomcat deployer and yes as you said without restarting. On the backend I stop the Tomcat then delete the old war file and insert the new one. Then i restart it

[Updated on: Thu, 25 June 2020 15:32]

Report message to a moderator

Re: Scout Application very Slow when 10+ Users are logged in [message #1829134 is a reply to message #1829133]

Thu, 25 June 2020 16:14

Claudio Guglielmo

Messages: 256
Registered: March 2010

Senior Member

Is it slow after a fresh restart of the Frontend server or does it get slow over time (after some deployments)? I don't think the backend server is the problem, there should not be a lot of concurrent threads running.

On the Frontend server, each active user creates a thread due to the long polling mechanism. So when more users log in more threads should be created. If that is not the case then this is likely your problem. Because now, a connection can only be processed as soon as one long polling connection is released (after 1 minute) because no more threads are created.

We experienced the same behavior with our demo applications (https://scout.bsiag.com/widgets, etc.). After about 1 week the apps got very slow and the currentThreadCount stopped increasing at about 10 threads. We deployed the demo apps nightly using the Tomcat deployer. About 2 weeks ago we temporarily deactivated the deployments and the apps are still running fine. For our real apps (not demo apps) we never use the tomcat deployer, that is probably why they are running fine...

Unfortunately we still don't know what the problem is, whether it is because of Tomcat 9, JDK 11 or Scout 10. It worked well with Tomcat 8, JDK 8 and Scout 9...

What JDK do you use?

Report message to a moderator

Re: Scout Application very Slow when 10+ Users are logged in [message #1829136 is a reply to message #1829134]

Thu, 25 June 2020 16:36

Luis Nothvogel

Messages: 56
Registered: October 2019

Member

Thank you for your answer. I will look into the Frontend server as soon as possible. I just have to wait for my coworker.

Quote:

What JDK do you use?

We are using OpenJDK 11

Report message to a moderator

Re: Scout Application very Slow when 10+ Users are logged in [message #1829138 is a reply to message #1829134]

Thu, 25 June 2020 16:49

Luis Nothvogel

Messages: 56
Registered: October 2019

Member

So I looked into the FrontEnd Tomcat Manager and there i see that the ThreadCount never goes above 10. Even when 10+ User are logged in. That might be the problem.

Do you know a Solution to this? I didnt find a Property in the Config Properties to change this behaviour.

Report message to a moderator

Re: Scout Application very Slow when 10+ Users are logged in [message #1829144 is a reply to message #1829138]

Thu, 25 June 2020 18:33

Luis Nothvogel

Messages: 56
Registered: October 2019

Member

Ok so the solution at least for us was indeed restarting the Tomcat of the Frontend. After that everything worked fine.
We also tested that after it worked, we deployed through the Tomcat deployer and then we had the same problem again. So it seems if you deploye through tomcat you need to restart it aswell. Dunno why but well at least it works now.

Report message to a moderator