When a table is marked

cacheable

the results of a scan are saved and used for every query with a >= interval, so the cost of

launchd

is amortized (based on the lowest interval of a scheduled query using

launchd

) across all uses of

launchd

in your schedule.