Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Optimal Values for "Total Threads" and "Chunk Size" of Absence Batch Parameters

in Workforce Management

Summary:
Hello,

Under "Configure Absence Batch Parameters", I understand that "Total Threads" and "Chunk Size" should be based on the population. However, how to know total available threads in Fusion instance? Are they static for all Fusion environments?

For the example mentioned here: "https://appslab.blogspot.com/2019/05/hcm-payroll-extracts-performance.html#:~:text=Threads%20are%20a%20number%20of,before%20retrieving%20the%20next%20chunk.", for 24000 employees, recommended total threads are 24000/400=60 and chunk size is 400. But will the system have 60 threads available to run the process efficiently?

As per Oracle Doc ID 2153518.1, total threads for Absence are recommended between 5 to 8 and chunk size between 20 to 30. This document was published in 2016 so I believe there must be some updates.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!