4 Answers:
Hi,
I'm sorry to hear you're not getting the performance you expected from the Jaspersoft server. We have many users and use cases of successful large deployments with high performance so I'm confident we can, with some more details, identify the root cause for the issues you outline.
RedShift is indeed a very fast BigData DWH, however, there are a few places performance issues can initiate, from the queries optimization, cache settings and Jasperserver configuration. Can you answer the following questions:
- Are you experiencing the issues in reports or when using Ad-Hoc data exploration
- Are you trying to list 1,000,000 rows or are you aggregating them?
- Is the issue happen when rendering a large table of data, chars or both?
- Can you share the configuration of your AWS Ad-Hoc (Go to Manage -> Server Setting -> Ad-Hoc settings)
- Ad Hoc Dataset Row Limit
- Ad Hoc Query Timeout (seconds)
- Optimize Queries for Domain-based Reports
- Optimize Queries for JDBC-based Reports
With this information we can begin estimating where the issue may be located and focus our next steps.
Thanks,
Assaf
Hi, thanks for the answer
- Are you experiencing the issues in reports or when using Ad-Hoc data exploration: In both.
- Are you trying to list 1,000,000 rows or are you aggregating them? The data source is much larger, has 70 million of databut aggregated data reach the million.
- Is the issue happen when rendering a large table of data, chars or both? Large tables
- Are you trying to list 1,000,000 rows or are you aggregating them? The data source is much larger, has 70 million of data
- Can you share the configuration of your AWS Ad-Hoc (Go to Manage -> Server Setting -> Ad-Hoc settings)
- Ad Hoc Dataset Row Limit: 1000000
- Ad Hoc Query Timeout (seconds): 3600
- Optimize Queries for Domain-based Reports: checked
- Optimize Queries for JDBC-based Reports: checked
Thank you for the extra details. I have a few follow up questions based on the above.
- When using ad-hoc, are you using Topics or Domains?
- Can you please attach a screenshot of your ad-hoc cache after trying to run one of the reports which fail. (Go to manage -> server settings -> Ad-Hoc Cache -> Find your query). If you cannot add a screenshot, please share the results for the following:
- Query/Fetch
- Memory Used
- Rows (Click on the query to get this data point)
- Please share the server logs for your query execution, to configure the server to track your execution do the following:
- As superuser, go to Manage/Server settings/Log settings, and set the following to DEBUG:
- Ad Hoc cache activity (CachedData): Logs the lifetime of cached data sets
- Ad Hoc AJAX requests (adhocAjaxRequests): Logs details about server requests for the Ad Hoc UI, including timings
- Run your ad-hoc report
- Search Jaspersoft server log for the events above (use name in parenthesis as the search term, i.e CachedData)
- Post the results
- As superuser, go to Manage/Server settings/Log settings, and set the following to DEBUG:
Thanks,
Assaf
Hi,
- When using ad-hoc, are you using Topics or Domains? Domains
thanks