AWI v24.4 load and performance

[Ivan Barumov]

We upgrade our systems to v24.4 from v21 last month but since then AWI performance issues are quite frequent.

just for perspective and info we are running red hat 8.10  java 17   and tomcat 9  load balanced servers and multiple AWI instances.

Before the upgrade we ran Test stage for months  with same settings and configs but did not observe any performance degradation (best guess is not sufficient stress).

As soon we brought the first  customer stage to v24 we needed to increase XMX value for the RAM tomcat uses double  as well more to the AE process. 
That helped for less then a day and we needed to increase again and again  until we start hitting open file limits . Increased limits as well but did not helped  much.  Only thing that helps for the moment is restart of tomcat but if you leave it more than a day issues start to appear again.

What we observed is open file held by the tomcat process does not go down /perhaps it does but extremely slowly/ every time you check the count will be higher.  Ram usage is a lot higher than before we stopped increasing it at x4 compared prior to the upgrade  and its running on the max side. CPU utilization increases as well depending on how long process is running day old  1 core less than 50 %  2+ days  multiple core 5+  full usage.

Its not normal  utilization of the AWI to be so demanding and different than before.  What are your experiences with v24 AWI ?

Did you notice  need of more recourses? how about the frequency of the tomcat restart you need to take ?   

and that goes without saying any helpful solutions  to be shared ?

-------------------------------------------

[Antonio Cesar dos Santos]

When we upgraded to version 24, we experienced performance issues.

 

Apply these two actions to improve.

- How to rebuild AWI Index's

Broadcom		remove preview
How to rebuild AWI Index's For V12.x Stop the JCPs. Remove the directory "indexCache" or "indexCache-12.X" from the bin directory of the Automation Engine. Start the JCPs which will rebuild the index from scratch. The first started JCP on a node will take over this role. View this on Broadcom >

- https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/21.0.8/CDA%20Guides/Content/AWA/Admin/admin_types_of_server_processes.htm#:~:text=Changing%20Work%20Processes,of%20work%20processes%20(WPs).

Note:

In my environment, we no longer use Tomcat at AWI. We use AWI's proprietary Automic.

------------------------------
Cesar
Dock Tech (Brazil)
------------------------------

[Keld Mollnitz]

Hi @Ivan Barumov,

out of curiosity, did you upgrade to v24 on the same hardware ? If so, are you able to compare the "performance numbers" in the WP logs before and after the upgrade?

For reference, here are the "performance numbers" for my v24.4.1 HF1 Sandbox env.:

20250806/154534.884 - U00003533 UCUDB: Check of data source finished: No errors. Performance CPU/DB: '25286853'/'1130 (1000/0.884786 s)'
20250806/154534.884 - U00003544 UCUDB: Reference values tested with Linux x64 on XEON 3600 MHz: CPU 525716336, DB 3505
20250806/154535.205 - U00003524 UCUDB: ===> Time critical DB call!       OPC: 'OPEN' time: '3:077.823.400'

Best regards

Keld.

-------------------------------------------

[Michael A. Lowry]

We are also experiencing performance problems in the AWI after upgrading a system from v24.3 to v24.4.

These functions of the AWI are impacted:

1. Logging in
2. Accessing the contextual menu for (right clicking on) an object or task
3. Process Monitoring perspective
4. Object search
5. Task search

The DB and underlying infrastructure (Kubernetes) is exactly the same as before.