Skip to main content
Question

Background Job Performance Degradation After Transitioning from IFS 10.14 to IFS Cloud

  • Nov 19, 2026 8:06 AM UTC
  • 2 replies
  • 21 views

Forum|alt.badge.img

Hi everyone,

We are currently transitioning from IFS Applications 10.14 to IFS Cloud, and we have encountered a significant performance issue with background jobs during our shipment creation process.

Our shipment process relies heavily on background jobs to add customer order lines with existing handling unit reservations to shipments.

The process executes background jobs individually, meaning that a separate background job is triggered for each handling unit.

In IFS Applications 10.14, processing 23 handling units would typically take no more than one minute. However, when testing the exact same process in IFS Cloud, it takes over an hour to complete.

I have already checked the Batch Queue Configuration and tried increasing the process count, but this did not result in any noticeable performance improvement.

Has anyone encountered a similar issue when transitioning from IFS Applications 10 to IFS Cloud?

Are there any additional configurations, performance optimization options, or architectural differences in background job processing that we should take into consideration?

Any insights or suggestions would be greatly appreciated.

Thank you in advance!

2 replies

Forum|alt.badge.img+10
  • Hero (Employee)
  • Nov 19, 2026 7:21 PM UTC

This issue, i.e. slow performance of background jobs, is seen from time to time by IFS Unified Support.  Features of IFS Cloud which often are involved with this condition are:

  • failure of the various cleanup jobs, i.e. Heavy Cleanup, Light Cleanup, etc. to be run as scheduled
  • failure to regularly run the database maintenance jobs such as VALIDATE INDEXES, REBUILD INDEXES,, GATHER STATISTICS, etc.
  • Lobby queries which need to be performance tuned - or perhaps run less frequently - as part of adoption of the new Cloud environment
  • Batch queues which may have undetected scheduling bottlenecks
  • Reports, particularly custom reports, which may have poorly tuned backend SQL queries

 Also review the Knowledge Base articles KB0049204, KB0073215 and others by using the keyword “performance” in your search of the KB database.

If your Cloud environment still performs poorly after completing needed changes made through review of the above topics consider opening a case with IFS Support to request a more in-depth investigateion of your Cloud environment.  If your Cloud environment is hosted by IFS you could also create a case to request running of an AWR report for your Oracle database of this environment.  Other 3rd party hosting services would likely also have the option to run AWR for you as well.  This report would identify any SQL queries which are consuming high database resources.  It may be that the Oracle database of your new environment needs to be tuned or needs one or more special indexes to accommodate custom reports.  Middleware configuration also can require modification due to the specific needs of some IFS customers.

A custom report can require additional indexes in a new database if it uses columns which were changed, modified or underlying indexes were modified as part of the version upgrade.  This is often the case when version upgrades are performed.

For a more detailed response to chronic performance problems feel free to provide your Cloud release level including Service Update (SU) level.  IFS Support can assist with in-depth analysis if you were to create a new case for this performance issue.  IFS Managed Cloud Services has multiple diagnostic tools to assist with database performance issues of our IFS customers who have IFS managed environments.  IFS Unified Support stands ready to help with situations such as those you’ve described in your initial post.


Forum|alt.badge.img+10
  • Hero (Employee)
  • Nov 19, 2026 7:24 PM UTC

P.S. - increasing the Processes count of a Batch Queue is not generally recommended.  Before making such changes be sure to check with your systems administrators to confirm whether or not the host machine(s) of your IFS Cloud environment have sufficient resources, i.e. CPU, memory, I/O capacity, etc, to accommodate an increase in the processes count of any Batch Queue.