Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
PaoloGuerra
Creator
Creator

System requirements for large files

We have QlikSense Desktop for Analytics on csv files.

We have problems with errors and freezing in the indexing phase.

What is the System requirements to index csv files for a total of 15/20 gb?

This is the hardware currently available. 

  HP Laptop
CPU Intel(R) Core(TM) i5-10310U CPU @ 1.70GHz
CPU release date 01/05/2020
N. CPU 8
Max Clock Speed 4.40GHz (con Intel Turbo Boost)
RAM 16 GB
Disk 500 GB

We also have the ability to install virtual machines.

Can we help me please?

Labels (3)
1 Solution

Accepted Solutions
Daniele_Purrone
Support
Support

Hi @PaoloGuerra ,
the first thing to consider is that the Qlik Sense engine is an in-memory tool, so you'll need enough physical memory to handle the data. Virtual memory is usually not an option.

Then it depends on what the data is about, and what you'll do with it.
The Engine stores unique values only once, so, after a while, the curve for RAM usage flattens.
https://community.qlik.com/t5/Qlik-Sense-Documents/The-data-scalability-of-Qlik-s-in-memory-associat...


You can probably test this by adding "FIRST" before the load statement, followed by a limited number of records.
https://help.qlik.com/en-US/sense/February2022/Subsystems/Hub/Content/Sense_Hub/Scripting/ScriptPref...

Test it with a certain number of records, check the resource usage, then do subsequent tests with a larger number of records until you get an idea of what the curve will look like.

Daniele - Principal Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.

View solution in original post

1 Reply
Daniele_Purrone
Support
Support

Hi @PaoloGuerra ,
the first thing to consider is that the Qlik Sense engine is an in-memory tool, so you'll need enough physical memory to handle the data. Virtual memory is usually not an option.

Then it depends on what the data is about, and what you'll do with it.
The Engine stores unique values only once, so, after a while, the curve for RAM usage flattens.
https://community.qlik.com/t5/Qlik-Sense-Documents/The-data-scalability-of-Qlik-s-in-memory-associat...


You can probably test this by adding "FIRST" before the load statement, followed by a limited number of records.
https://help.qlik.com/en-US/sense/February2022/Subsystems/Hub/Content/Sense_Hub/Scripting/ScriptPref...

Test it with a certain number of records, check the resource usage, then do subsequent tests with a larger number of records until you get an idea of what the curve will look like.

Daniele - Principal Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.