Information on Yearly Calendars Intervals
1. How much memory does a yearly interval consume?
Follow wiki # 597 on Monitoring server start-up to get information on cached collections.
It is possible to measure the amount of memory taken by the calendars collection and calculate how much memory your yearly intervals consume.
2. How many yearly intervals can be created per calendar?
The maximum number of yearly interval depends on the database limitation. The table maximum size can be found with the following query:
SELECT COLLECTION_ID, name, decode (floor(Collection_ID/7),0 ,’134217728(128M)’,’1048576(1M)’) “Keys Limit”
where name = ‘W6CALENDAR_YEARLY_INTERVALS’
3. Are yearly intervals loaded and cached on the client side for each resource loaded in the Gantt?
Yes, the client store the yearly intervals as an internal class and not ‘W6CPTimeInterval’.
A W6CPTimeInterval object specifies a period of time by a Start date and time and a Finish date and time.
The internal class cannot be accessed while W6CPTimeInterval object can be accessed using client API.
4. What is the server side memory load? are all yearly intervals cached for all calendars in the system?
All the yearly interval in the database are loaded and cached when each Service Optimization server starts (including normal calendars, base calendars, Engineer & Task calendars, even old ones, orphan ones, and ones referenced by inactive engineers), so the memory load depends on the number of the yearly intervals in the database.
5. If a yearly interval is created on the client side is it automatically added/updated in the dllhost cache or does Dllhost have to be restarted?
The new yearly interval is indeed being added to the server’s cache and dllhost process doesn’t need to be restarted. The server refresh mechanism takes care of loading new objects to RAM based on their revision.
6. Can Calendars and Calendat Intervals be deleted?
The Purge agent(s) needs to be configured for Tasks & Engineers associated calendars and calendar intervals to be automatically removed once expired (per setting).
The Purge agent, however, only purges the calendars and calendar intervals of the selected groups of Tasks & Engineers. Also, the purge agent was only designed to purge referenced calendars. Orphaned calendars that are not associated by any Task or Engineer shall not be automatically deleted, nor Base calendars (referenced only by other calendars – not by Tasks or Engineers). In order to remove orphaned and base calendars with their intervals, please refer to wiki # 605.