Home > Storage > PowerScale (Isilon) > Industry Solutions and Verticals > Electronic Design Automation > PowerScale: Best Practices for Semiconductor EDA Design Environments > Job Engine
A logical inode (LIN) is a piece of metadata. Some OneFS system jobs have two types: one that processes at the block level, and one that processes at the metadata level. There is a setting that allows the job engine to force one level or the other.
The effect on running jobs can be substantial, and the difference between an AutoBalance and an AutoBalanceLin on a system with SSDs can be large as well. The time it takes to run some jobs can change from multiple days to a single day or less.
OneFS 9.2 and later versions default to running the Lin-based version of the AutoBalance and FlexProtect jobs when these jobs start automatically, where appropriate.
For systems with metadata acceleration (RO or RW, and not L3), use LIN-based jobs for optimal performance. Some jobs may be faster using LIN-based with L3 acceleration. This is because the job is changing its processing method from block-based to metadata-based. L2 and L3 hit rates for metadata may still be high enough to warrant the change.
The job engine should start LIN-based jobs, as shown in the following setting. (Auto does not perform this setting.)
isi_gconfig -t job-config jobs.common.lin_based_jobs
EDA design workflows use could benefit from using an EDA_OFF_HOURS schedule based on the typical off hours for your specific environment.
isi_gconfig -t job-config jobs.common.lin_based_jobs=true