Is there any advantage of switching from SYSPLEX to CACHE in ACF2

Products

• ACF2

Issue/Introduction

Would there be any performance improvements by switching from SYSTPLEX to ACF2 CACHE? 

Resolution

The cache storage can be primed with all logonids with one entry in the LIDSPRIM record LIDS(-)
The sysplex is populated on an on-demand basis.

One item that is slowed with the ACF2 CACHE is when processing in sequential mode. That is because the ACF2 SVC has to queue the
I/O request to the ACF2 CACHE I/O processing module in the ACF2 address space. This adds some latency to the overall processing time.

Note that using the cache would eliminate the AES256 contention as long as the logonid is in the cache.

PTF LU10692 changes the polling interval for the synchronizer to be 1/2 second increments instead of 1 second.
The synchronizer is only needed if you are sharing databases.

The GSO OPTS BYPSTATS should be set to prevent an overrun of the CACHE I/O processing due to updating of the last access stats.
BYPSTATS specifies whether to update the logonid last-access information for the signon request.
The SMF record is written when the logonid update is being bypassed.
LAST ACCESS updates only occur once a day.
Once the LIDREC is in storage all updates to the ACF2 DB are async in nature.
 
It is suggested that only logonids need to be primed.
infostg and access rules can remain added on demand as most processing is done using records that are already resident .