Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
7 replies
Subscribers
4 subscribers
Views
6332 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Reports
Query Process Analytics getting time out
shailjas
over 8 years ago
Hi,
We have a task report, even if the filters are applied to the report it is fetching all the data.
Since the number of active tasks for the application is more than 1000, it increases the CPU utilization.
We are receiving some warning logs because of this.
snippets from the logs : "Total: Total (Report named 'CIC Tasks Report' (report document id 14972), maximum report time 2000ms) affected 694 rows"
To reduce this we are thinking of reducing the unnecessary columns from the report and to increase the timelimit in custom.properties for this.
Can someone help regarding this.
OriginalPostID-231189
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 8 years ago
@shailajas In this context, what I meant to say is, each query should be made afresh with the changed pagingInfo. That is, while loading the report, you will fetch only 25 rows (let's assume you are asked by Business to show only 25 rows per page) in the load(). Get the next 25 rows only when the user tries to paginate, and this should be written in saveInto of the Report Grid. This way, you will hold only 25 rows in the memory or query 25 rows each time. In this case, definitely, there won't be an issue at all even though the columns are many in the process report and further hold complex and time consuming expressions.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 8 years ago
@shailajas In this context, what I meant to say is, each query should be made afresh with the changed pagingInfo. That is, while loading the report, you will fetch only 25 rows (let's assume you are asked by Business to show only 25 rows per page) in the load(). Get the next 25 rows only when the user tries to paginate, and this should be written in saveInto of the Report Grid. This way, you will hold only 25 rows in the memory or query 25 rows each time. In this case, definitely, there won't be an issue at all even though the columns are many in the process report and further hold complex and time consuming expressions.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data