[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29283#action_29283
]
Jan Haderka commented on MAGNOLIA-3267:
---------------------------------------
Hi Matthew,
this looks really strange. You probably want to move this issue to the
Support-Magnolia project as described at
http://documentation.magnolia-cms.com/support.html
Once you have the access to the support, you don't need to recreate the isssue,
just simply move it (there is a "Move" operation on the left side of this page.
One change that happened between 4.3.1. and 4.3.5 is upgrade of the JackRabbit
to 1.6.2. - MAGNOLIA-3188. This might have an impact on repository indexes.
The way to test this would be to shutdown the server, remove all {{index}}
folders (the folders in {{
${magnolia.repositories.home}/magnolia/workspaces/*}}. Each workspace has one
index folder. I would recommend to just move those folders to other location
for now or simply rename them. Then startup the instance again.
Startup time will be longer since the complete repository will be reindexed.
How long it will take depends on the size of the repository and could be even
couple of minutes. You can observe the log files for exceptions during that
time to see if the indexing fails. If that is so, it usually means there is a
repository corruption and you would need to restore original indexes to deal
with that first.
Once the indexing is finished, server will continue with the startup. You can
then test the server to see if the CPU usage went down.
In case you are still experiencing high CPU load, it would be helpful to obtain
heap dump or the list of threads from the Tomcat including the stacktraces of
what java code they were executing. You should be able to narrow most of that
CPU usage to few threads.
> High CPU usage causing slow page loads 4.3.5
> --------------------------------------------
>
> Key: MAGNOLIA-3267
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3267
> Project: Magnolia
> Issue Type: Bug
> Environment: Red Hat, Tomcat 6
> Reporter: Matthew Arriaga
> Assignee: Boris Kraft
> Attachments: cpu_usage_author_past_week.jpg,
> cpu_usage_author_real_time.jpg
>
>
> I updated Magnolia EE from 4.3.1 to 4.3.5 after hours yesterday. When editors
> began logging onto the author instance this morning the CPU climbed to about
> 190%(two processors). CPU usage has ranged from 130-200% all day and the
> system has been very sluggish and difficult to use. When I shutdown tomcat,
> CPU usage goes down to a negligible level. When I start tomcat the load
> increases and then goes down again after the server is up. CPU usage is
> reasonable while using admin central, but when a page is opened CPU usage
> climbs above 100% for a few seconds(Maybe an stk issue?). The tomcat instance
> is running magnolia, lamda probe and the tomcat manager.
> Along with Magnolia, I added the latest version of the following modules
> during the update(They were all present in the running 4.3.1 instance):
> webdav, ldap, groovy, and openmind's simple media module.
> I updated a test system, but missed the high cpu usage. CPU usage does seem
> to be higher on the 4.3.5 test system as well. On the test system I tried
> uninstalling the media module, but when I remove the openutils-mgnlmedia from
> the lib directory I get the following error: 2010-08-03 10:57:13,168 ERROR
> info.magnolia.module.templating.RenderingFilter : Can't find renderer for
> type stk
> I have a single backup job scheduled to execute nightly, nothing under the
> modules/scheduler node is active.
> I deleted my cache and indexes on the test system, system is rebuilding the
> indexes.
> I don't see anything out of the ordinary in the tomcat logs.
> I looked through lamda probe's information, nothing really stuck out as a
> problem (although I'm not really sure what to look for).
> I'm not really sure what to do, other than recreate my 4.3.1 instances from
> backup(which I don't want to do).
> Any help you can give me, about where to look or what to do, in order to get
> the cpu down would be appreciated.
> Also, I don't know if the media module is causing the problem or not, but I
> just a soon uninstall it. I tried removing the config/modules/media node and
> removing the associated jars, but I receive the above error. Any information
> on what I have to do to remove the media module would also be appreciated.
> I've included CPU usage screen shots. The first shows the past week, running
> 4.3.1 and today after updating to 4.3.5(the drop is when I restarted tomcat.
> The second graph shows a real-time snapshot for the past hour.(With 4 active
> sessions reported in lamda probe)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
