-
assigned issue to
High CPU load after enabling plugin.
Looks like a couple hours after we enabled this plugin our CPU load (by Stash JVM) started creeping up, eventually getting to about load-average of 30. This didn't appear to cause any issues other than slight slowness in Stash.
Disabling plugin instantly decreases amount of CPU used by Stash and system load drops rapidly.
Our instance is relatively small (dozens of repos, dozens of users, maybe one pull request per hour?). I don't have too much freedom to debug things on a running system, but let me know what would be helpful. I did not see anything obvious in log files, but I can enabled JMX over the weekend and take a look there.
This is Stash 2.10.0 and plugin 1.2.2
Comments (13)
-
reporter -
I do not see any job running in background as the result of installing the plugin. Work is done only when users request a page. Plugin configuration is stored using ActiveObjects from atlassian and AO uses DB which might not be used if other plugins do not need it. Pure speculation really, but atm I cannot think of anything else. If you can provide some profiling info I might be able to look into this further.
-
I'm seeing the same thing. After enabling the plugin, CPU load began increasing over a two hour period until it got to around 15-20% load.
-
Can you provide specs for systems? JDK/JRE version, hardware specs, OS versions, etc.
-
- changed status to resolved
Fixes
#20, changed email notifier implementation, no idle threads→ <<cset 5ad73cc2edfb>>
-
I traced some (not quite as high as you described) CPU time on my instance to the notification part. 1.2.4 version has a fix for that. Please let me know if issue persists.
-
- changed component to Email notificaitons
- changed version to 1.2.4
-
Account Deactivated We still experience the high CPU load after installing the updated version.
-
Same here
-
- changed status to open
CPU load is still present
-
- removed component
- marked as blocker
-
I pushed out 1.2.5 with some performance improvements and am continuing investigating the cause of the high CPU load
-
- changed status to resolved
Will reopen if this will be reported for 1.2.6+
- Log in to comment