According to Qlik's best practices and as a rule of thumb: the more resources, the better, and that's why the removed this setting in QlikView 12. So using all CPUs should be fine even if they are at 100% for some time.
There are some actions, like saving a file or doing a JOIN which requires more CPU than usual, so it's completely normal to see the CPU usage spiking to 100% for a few seconds, then down to 20% (or even less) and then up again to 80%-90%. This is perfectly fine.
Factors that affect this usage are file size (saving files of several GBs takes a lot of resources), complexity of the script (aggregations, functions used, JOINs), size of the tables (dozens of columns with very distinct values), etc.
If for any reason this usage makes the system unstable, there are usually two reasons
- The script/data model/files are too big and they should be reduced or the environment needs more resources (e.g.: natural growth in complexity, or distribution service in the same computer than QlikView Server and increase in the number of users)
- There are other processes in Windows competing for those resources (antivirus mostly, but could also be a backup or snapshot software)
If none of those two are the case, then report to Qlik Support so they can investigate further.
.png "Miguel_Angel_Baeyens"){kind=avatar}
