Skip to main content
Question

IFS Cloud is slow

  • March 2, 2026
  • 1 reply
  • 45 views
L
Do Gooder (Customer)

Hi everyone,

 

Our IFS CLoud environment is getting worringly slow in some parts as we are working on Procurement (24R2). When we (the IT) try to spot it, we do see everything slowing down. Everything eventually works as it should, only slower than expected. We find no errors in our consoles. However our users (the people who use IFS daily) have alerted us that some processes end in failure because of the time out.

We worry because the slowing down happens consistently on our test environment, but these are new processes that will be used in production from next week on. We cannot afford to have the new tools go into time out as soon as they go online.

Sadly, we have no idea where to start with this issue. If anyone else has had issues of general slowing down, we would love to hear how you went about tackling the issue.

1 reply

L
Do Gooder (Partner)
Forum|alt.badge.img+6
  • Lingesan08
  • Do Gooder (Partner)
  • March 31, 2026

Hi ​@lbartolome ,

  This kind of general slowdown + occasional timeouts in IFS Cloud (24R2) is something we’ve seen before, especially during new process rollouts in Procurement.

Since:

  • No errors are logged
  • Everything eventually completes
  • But users hit timeouts

 This usually points to a performance bottleneck, not a functional issue.

 Where to Start (Most Important)

You need to identify which layer is slowing down:

  1. Database
  2. Application (IFS Cloud)
  3. Middleware / Kubernetes
  4. Client / Network

 Step-by-Step Troubleshooting Approach

🔹 1. Check Database Performance (Most Common Root Cause)

Look for:

  • Long-running SQL queries
  • Locks / blocking sessions
  • High CPU usage

 Focus areas:

  • Procurement processes often involve:
    • Purchase orders
    • Supplier queries
    • Inventory joins

Ask DBA to check:

  • Top SQL by elapsed time
  • AWR / ASH reports
  • Blocking sessions

🔹 2. Enable IFS Performance Logging

In IFS Cloud:

  • Enable performance tracing / logging

 Look for:

  • Slow projections
  • Long API calls
  • Heavy queries behind Aurena pages

🔹 3. Check Kubernetes / Infrastructure

Since you're on Cloud:

Check:

  1. kubectl top pods
  2. kubectl top nodes

Look for:

  • High CPU or memory usage
  • Pod restarts
  • CPU throttling

Common issue:

  • Pods under-sized → slow response but no crash

🔹 4. Review Timeout Configuration

Users hitting timeout means:

  • Browser timeout
  • Reverse proxy timeout
  • API timeout

 Check:

  • Ingress / load balancer timeout
  • Aurena / backend timeout settings

🔹 5. Test Specific Use Cases (Very Important)

Since issue is in new Procurement processes:

 Identify:

  • Exact screen / action
  • Example:
    • Create PO
    • Approve PO
    • Supplier search

Then:

  • Measure response time
  • Compare:
    • Test vs Production

🔹 6. Check Data Volume Differences

Often overlooked:

  • Test environment may have:
    • More data
    • Poor indexing
    • Different statistics

 Ensure:

  • DB stats are updated
  • Indexes exist for heavy queries

 Common Real Causes (From Experience)

 1. Missing Indexes

  • New processes → new queries → no indexes

 2. Heavy Customizations

  • Custom projections / logic slowing down

 3. Under-sized Pods

  • Especially for:
    • Aurena
    • Projection services

 4. DB Statistics Not Updated

  • Causes poor execution plans

 Quick Wins (Try Immediately)

  • Restart pods (temporary improvement check)
  • Gather DB stats
  • Increase CPU/memory for app pods
  • Monitor slow queries during peak usage

 Recommended Approach Before Go-Live

 Do this before next week:

  1. Run load test on Procurement scenarios
  2. Capture:
    • DB load
    • API response time
  3. Fix:
    • Slowest queries first
www.linkedin.com/in/lingesanr86
Terms & ConditionsCookie settingsAccessibility statement