Has anyone have positive/negative experience increasing the "conf.data.quer

Chris over 8 years ago

Has anyone have positive/negative experience increasing the "conf.data.query.memory.limit" property as a work around for memory threshold errors? We're running into problems with the default 1 MB data limit hit by queryEntity() when exporting data to excel via the Download Datasubset plugin. We have requirements to export large data sets to excel, but wanted to discuss performance concerns before we increase this setting - maybe server hardware configuration considerations, etc? Any concerns other than user experience, if we increase this to say 3-4-5 MB?

Discussion posts and replies are publicly visible

0 Myles Weber
Appian Employee
over 8 years ago

I have personally seen a lot of stability issues with raising that specific setting. I wouldn't change it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chris over 8 years ago

Thanks Myles. We are going to see if we can work with the users' requirements before heading down this path, was just curious if this has been implemented with decent results in the past.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 gauravg568 over 8 years ago

Is loading data into Excel as batches of data an option for your use case since a!queryEntity takes a!query as an input where the batch size can be specified? You could automate populating the entire dataset into Excel in batches.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chris over 8 years ago

Thanks, we may go that route but I was hoping to accomplish this right from the report with the Download Datasubset plugin. Batch population seems like it would require a process model instead, potentially the Start Process Writer could simulate the download link - we may go that route as well.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel