When setting up a new AAI environment or adding a new scheduler to AAI, how can I ensure I have enough resources allocated to AAI?
AAI
There is an AAI Sizing Worksheet available within the AAI documentation under Preparing for the Installation.
This sizing worksheet will use the following factors that may influence how much memory and cpu are required to efficiently run your AAI environment:
Scheduler instances and execution load
Total number of jobs in all the scheduler instances that you want to connect to AAI. depending on the scheduler types, depending on the scheduler types:
The total number of jobs in all instances of AutoSys, Automic, Control-M, CA7, ESP, and Tidal, (but not IWS) schedulers (line 3)
The total number of jobs in all IWS scheduler instances (line 4)
Percentage of job count growth per year (for example, 5%) for all schedulers
Total number of scheduler instances that you want to connect to this AAI server
Total number of job runs per day in all connected scheduler instances
Percentage of job run growth per year (for example, 10%)
Number of days of History retention
The last items in lines 10 and 11 apply only to a very large installation in which the execution memory footprint quickly becomes very big. In the worksheet they are both set to the AAI default value of 48 hours.
Hours of completed job runs in memory (server parameter recentRunsDuration: default 48 hours)
Hours of forecasted job runs in memory (server parameter forecastPeriod: default 48 hours)
Once you provide entries for the values above in the worksheet, the sizing worksheet will provide you with the minimum specifications for your AAI environment, as seen below:
It is very important to use this worksheet before rolling out a new AAI environment or adding a new scheduler to your AAI environment.
Not that this worksheet may be updated periodically, so make sure to alway visit the Preparing for the Installation section of the guide to ensure you have the lastest version.
If you are unable to access the AAI UI to get the total scheduler and job count, you can use the SQL queries below to retrieve this data directly from the AAI Database.
Scheduler Count
select count(*) from JobScheduler;
Total Job Count
select count(*) from JawsJob;
Last 7 days of JobRuns per day
The queries below can help gather this data from an existing environment if it is currently processing event data.
Oracle
SELECT
TRUNC(TO_DATE('1970-01-01', 'YYYY-MM-DD') + (startTime / 86400000)) AS run_date,
COUNT(*) AS Job_Runs_Per_Day
FROM JobRun
WHERE startTime IS NOT NULL
AND TO_DATE('1970-01-01', 'YYYY-MM-DD') + (startTime / 86400000) >= TRUNC(SYSDATE) - 7
GROUP BY TRUNC(TO_DATE('1970-01-01', 'YYYY-MM-DD') + (startTime / 86400000))
ORDER BY run_date DESC;
SQL Server
SELECT
CAST(DATEADD(ss, startTime/1000, '1970-01-01 00:00:00') AS DATE) AS run_date,
COUNT(*) AS Job_Runs_Per_Day
FROM JobRun
WHERE startTime IS NOT NULL
AND DATEADD(ss, startTime/1000, '1970-01-01 00:00:00') >= DATEADD(day, -7, CAST(GETDATE() AS DATE))
GROUP BY CAST(DATEADD(ss, startTime/1000, '1970-01-01 00:00:00') AS DATE);