nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD sucking up CPU

speck

We are running

Interwoven TeamSite 6.5.0 Service Pack 2
Interwoven OpenDeploy Version: 6.2.1.0.0 Build 71309

and we are seeing absolutely abysmal perfmance, OD server is sucking up 50% of the system CPU and showing virtual footprints of well over 1/2 a gig. Restarting it seems to calm it down until the first deployment is executed, then it rapidly ramps up its CPU useage and it footprint expands.

This is obviously affecting everything on the server, to the point where just navigating the file system is a painfully slow process let alone actually trying to use Teamsite itself.

Has anyone seen anything like this before? Any ideas?

Thanks,

Sean

Find more posts tagged with

Comments

jed

Maybe OD is running low on memory and spending lots of time garbage collecting? Of course, the question is what is causing the memory issue. Anyway, to see if this is the case, you can update the $odhome/processod file to add GC collection stats:

-Xloggc:/logs/gc.log
-XX:+PrintGCTimeStamps
-XX:+PrintGCDetails

speck

Ok, have figured it out, the event subsystem was not configured with an expiry time, so Teamsite was scanning over 1 million records without use of indexes routinely and killing the system.

We purged the messages and message_handles tables and things are working fine

We have added the expirytimeindays setting and run the restart, but the message table still does not have anything but '0' for values in the expirytime column. Not sure if its supposed to have something or not.

We are only using DataDeploy and not Reporting or Search, is there a way to configure the event subsystem not to write messages for reporting and search? Only write messages for datadeploy (ddsub consumer)? I can't find this sort of configuration setting mentioned in any documentation for Teamsite or OD.

Sean

Adam Stoller

...
We are only using DataDeploy and not Reporting or Search, is there a way to configure the event subsystem not to write messages for reporting and search? Only write messages for datadeploy (ddsub consumer)? I can't find this sort of configuration setting mentioned in any documentation for Teamsite or OD.

Sean

Are you using DAS or just command-line oriented DataDeploy?
If you're not using Reporting, Search, or DAS - you could probably just disable the event subsystem altogether and not have any issues.

speck

We are using DAS.

There seems to be 2 issues here, one how if at all can we tell the system not to write messages for anything other than DAS, is this possible? and 2, even after adding expirytime to the config it is not being written to the DB, expiry time as I understand it should be createtime + number of days that expiry is set to, yet even after setting the expiry time the message expiry time column continues to always be 0, is this a known issue/bug?

Sean