Logon process optimization
Posted: Thu Jul 04, 2019 5:10 pm
Hi,
There could be helping a feature that pre-populates cache by blocks needed during the logon process. (=blocks required during + say 5 minutes after the logon).
There are 2 use cases:
1. For nonVDI/normal scenario: The cache is be pre-populated opportunistically on the background of the logon dialog. (e.g. if user hesitates to insert his credentials.)
2. For use on VDI scenario: The cache gets pre-populated during the boot process to improves user experience as: A. VDI's boot the process is not visible to user; B. Logon credentials are submitted automatically (hence no "user hesitation as in scenario 1), C. Logon process is visible to user.)
In both cases, this should help to improve the duration (or perception) of the logon process as well as the launch of first apps.
Of course this assumes, that primocache tracks and maintains the list of blocks access during the boot/logon.
btw: I just noticed you demonstrated the similar concept here. https://www.romexsoftware.com/en-us/pri ... -time.html (Except that you do not use precaching but L2 cache populated on the last boot. )
There could be helping a feature that pre-populates cache by blocks needed during the logon process. (=blocks required during + say 5 minutes after the logon).
There are 2 use cases:
1. For nonVDI/normal scenario: The cache is be pre-populated opportunistically on the background of the logon dialog. (e.g. if user hesitates to insert his credentials.)
2. For use on VDI scenario: The cache gets pre-populated during the boot process to improves user experience as: A. VDI's boot the process is not visible to user; B. Logon credentials are submitted automatically (hence no "user hesitation as in scenario 1), C. Logon process is visible to user.)
In both cases, this should help to improve the duration (or perception) of the logon process as well as the launch of first apps.
Of course this assumes, that primocache tracks and maintains the list of blocks access during the boot/logon.
btw: I just noticed you demonstrated the similar concept here. https://www.romexsoftware.com/en-us/pri ... -time.html (Except that you do not use precaching but L2 cache populated on the last boot. )