You can use specify flex.bi advanced settings in the config/eazybi.toml
configuration file. The configuration file uses TOML format. Please see comments and commented examples for each section in this file.
On this page:
toc
Performance optimization and tuning
Increase query timeout
By default, there is 60 seconds query timeout after which report generated queries will be canceled. The purpose of this timeout is to avoid too long execution of too complex ad-hoc queries (when you join too many dimensions in rows or columns).
Note |
---|
If you have reports that fail the query timeout error and you need help optimizing these reports, then please export and send the report definition to flex.bi support. |
If you still would like to increase this timeout value then change the default 60 to a different value:
...
Code Block |
---|
[source_application.sql] connect_timeout = 20 read_timeout = 600 query_timeout = 600 |
Increase concurrent report queries
The default number of max concurrent flex.bi report queries is 10. If more MDX queries are made simultaneously, then new queries will wait until previous will finish.
If you have a powerful server with many CPU cores and you would like to allow more concurrent MDX queries then you can increase max queries value in eazyBI advanced settings with:
Code Block |
---|
[mondrian] "mondrian.rolap.maxQueryThreads" = 20 |
If you change several Mondrian settings then use just the one [mondrian]
section.
Enable Mondrian debug logging
If you would like to debug Mondrian MDX queries, that are generated by flex.bi, or to see all executed SQL statements then you can enable Mondrian MDX and SQL logging with
...
You can see the Mondrian debug log in the log/eazybi-mondrian.log
file.
Enable Mondrian request profiling
Note |
---|
Available from the flex.bi version 5.0. |
...
Code Block |
---|
[mondrian.profiling] enable = "system_admin" |
Then, go to the Analyze tab and Enable profiling in the other report actions dropdown. After that, every next request execution will be profiled and you can view the last profiling result with Show profiling result.
...
Currently, Mondrian request profiling for reports in accounts with a custom schema will not include SQL queries that are generated by Mondrian. In other accounts, SQL queries are filtered by standard table schema prefixes but in custom schemas currently there is no standard way how to identify these Mondrian queries.
Background job queues
There are several background job queues in flex.bi:
- regular_import – for source application imports that are scheduled at a regular frequency.
- application_import – for source application imports that are started manually.
- file_import – for uploaded source file imports.
- dashboard_email – sending emails for dashboard email subscriptions.
You can see the status of background job queues from the flex.bi System administration / Background jobs page.
By default, one parallel background job can be executed in each queue. If you would like to increase the size of the queue, then specify size
the setting for this queue, for example:
Code Block |
---|
[job_queue.application_import]
size = 2 |
If you would like to limit that no background jobs are executed during some hours (e.g. during high load hours of Jira) then specify either disabled_hours
or enabled_hours
the setting, for example:
Code Block |
---|
[job_queue.application_import]
disabled_hours = "9-18" |
or
Code Block |
---|
[job_queue.application_import]
enabled_hours = "0-9,18-24" |
In both cases, manual data imports will not be done from 9:00 to 18:00 (using the Jira server time zone).
If you change disabled_hours
or enabled_hours
, then it will be checked every 10 minutes.
Enable Mondrian to debug logging
If you would like to debug Mondrian MDX queries, that are generated by flex.bi or to see all executed SQL statements then you can enable Mondrian MDX and SQL logging with
Code Block |
---|
[mondrian.log]
"mondrian" = "ERROR"
"mondrian.mdx" = "DEBUG"
"mondrian.sql" = "DEBUG" |
You can see the Mondrian debug log in flex.bi home directory log/eazybi-mondrian.log
file.
SSRF protection
Note |
---|
Available from the flex.bi version 5.0. |
...