How to increase calculation time to solve "Calculation timed out error"???

[#1]

Hi Friends,

We are having Multiple applications with huge database . 

application shows Error :

  "Calculation timed out error"

"Calculation timed out"? Not during reload. This error occurs in front end.

We are using filter panes for sorting data but it is quite difficult to select always.

How to solve this error?

or How to increase calculation time on server?

Please help to solve.

[Lech_Miszkiewicz]

Hi,

I would review expressions in first place. Very often we forget how we can levarage set analysis capabilities to speed up calc time, for example where our FACT table is a composition of many sources concatenated together. Then it is important that each of the source is flagged in FACT or linked table and used in set analysis expression like:

f.ex (source = 1 --> Sales only data)

sum({<source={1}>} Sales)

This is very often huge boost in timecalc.

Also review your datamodel whether you have some sort of dataisland calendar or other detached filter. They also slow down calc time a lot and you may reconsider your datamodel and try to achieve snowflake or star schema.

If it is already by the book, look at the CPU cores and RAM

Now coming to your question:

I dont think such settings exists.

regards

Lech

[Lech_Miszkiewicz]

Hi i forgot to add that it is worth to implement calculation conditions on objects!

hth

regards

Lech

[kji]

You can change the time limit by adding a line

ObjectTimeLimitSec=NN

under the [Settings 7] section in the servers settings.ini file.

By default NN=60 for server but is unlimited(-1) for desktop.

This is limited on servers due to performance concerns so using calculation conditions is the reccomended way when possible.

[vinieme12]

can you post a snapshot of your table details

Go to Settings >> Document Properties >> Tab "Tables"

also is this a single object you are referring to or all objects?

[boguslaw_gmitru]

Of Course, the best way is to try optimizing your application, as Lech wrote.

From November 2017 You can otherwise change the timeout in the QMC --> Engine --> Advanced --> Hypercube time limits (seconds)
If you set this value to 0 then you will disable the timeout. Else, you may set it to 120 seconds.

After making this change, then you will need to restart the Qlik Sense Engine and Qlik Sense Service Dispatcher on all nodes where this setting is changed.