Read and write of QVD files to DataFiles in Qlik Cloud is perceived as slower than similar file read and write in client-managed Qlik Sense Enterprise on Windows.
Environment
Resolution
In long term, Qlik is evaluating options to further improve the data file performance and at the same time remain compliant with the required security standards.
For app reloads that finish within app reload timeout and reload interval ther is genrally no need to take further actions, as the the reload task will still be successful at data refreshed as expected.
For app where app reload time is a challenge, an intermediate approach to mitigate the file encryption effect of QVD storage in Qlik Sense Enterprise SaaS deployments might be;
- Review QVD layer strategy
QVD files may have grown in size over time and become almost monolithic and not optimized for the actual use cases. Evolving the QVD layer to a more granular structure with more and smaller files the impact of file I/O can be limited. For example, splitting sales data in QVDs per year can speed up reload times and also enable reading less data for apps that only require data points from the latest years.
- Alternate file storage
Qlik currently does not provide a tenant-level option to disable disk encryption due to compliance requirements. An alternative can be to review non-encrypted file storage options in the public cloud or on-premise if DataFile read and write performance becomes a critical issue.
See Qlik Web Storage Provider Connectors for a supported file storage location for easy and optimize file load in a Qlik Sense Enterprise SaaS app.
It is importnat to ensure that file storgae solution is deployed geographically close to, or ideally in the same region as, the Qlik Sense SaaS tenant to avoid latency becoming a problem.
Important: Qlik can not make specific recommendations on alternative file storage. Local IT security policy should be considered when storing business data in any public cloud-based storage location.
Cause
Storage in Qlik Sense Enterprise SaaS must be encrypted on file level as part of current compliance requirements, which also limits the number of compliant encryption libraries. See Trust and Compliance at Qlik, https://www.qlik.com/trust, for more details.
Internal Investigation ID(s)
