Skip to main content
Solved

Questions relating to Schedule Board performance

  • August 30, 2022
  • 2 replies
  • 122 views

Forum|alt.badge.img+7

Hi,

Can I get any answers to the following questions?

1. From Oracle19c, an auto indexing function has been offered. Is this recommended by IFS to use for periodic index rebuilding?

2. What exactly does the the WIZARD_RESCHEDULE_NOT_ALLOWED app param do and it's effect on the schedule board? Any other app params that may affect Schedule Board performance?

 

Thank you,

Kulunu

Best answer by Aaron.Sleight

The WIZARD_RESCHEDULE_NOT_ALLOWED app param does not impact the schedule board in any way.

 

The largest contributors to schedule board performance are:

  1. Amount of resources/teams being displayed (lower the better)
  2. The period of time being displayed (shorter the better)
  3. How frequently the SB is set to auto refresh (less frequently the better)

 

Each of those is controlled through the settings on the schedule board itself, not application parameters.

 

Additionally, there have been several changes to improve the performance of the SB.  If you are not already running the latest FSM 6 update, you should strongly consider adopting that.

 

2 replies

Aaron.Sleight
Hero (Employee)
Forum|alt.badge.img+14
  • Hero (Employee)
  • Answer
  • August 30, 2022

The WIZARD_RESCHEDULE_NOT_ALLOWED app param does not impact the schedule board in any way.

 

The largest contributors to schedule board performance are:

  1. Amount of resources/teams being displayed (lower the better)
  2. The period of time being displayed (shorter the better)
  3. How frequently the SB is set to auto refresh (less frequently the better)

 

Each of those is controlled through the settings on the schedule board itself, not application parameters.

 

Additionally, there have been several changes to improve the performance of the SB.  If you are not already running the latest FSM 6 update, you should strongly consider adopting that.

 


Forum|alt.badge.img+7

Thank you @Aaron.Sleight for the detailed response!