An explanation of non-optimized access
An explanation of non-optimized access
There may be times when an end user notes a lot of "Non-optimized Access" entries in the event log. Conversely, the user may notice poor performance on specific SAN LUNs or the entire Axiom and numerous non-optimized access events are noted by the event log.
Every LUN on the Axiom has an owning Slammer Control Unit. Inside this Control Unit (or CU for short) is that LUN’s cache and access data. Optimized access is taken through the Fibre Channel or iSCSI ports on that CU. If access for a LUN is requested from a port that is not on the owning CU, that is called Non-optimized access. The request needs to be forwarded to the owning CU, which takes CPU overhead from both CUs and causes an overall lag of the total system