batching the query

Hi,
I want to know how does exactly batching the query will work in Appian in retrieve the larger data ?

OriginalPostID-256157

  Discussion posts and replies are publicly visible

Parents
  • Be mindful that if you increase the default "conf.data.query.timeout" and"query.memory.limit", you increase the risk of having long running queries that Application Users perceive the Application to be 'frozen' or broken... Please look at redesigning or optimizing your query before changing any settings, and note that for Appian Cloud, these settings are locked down/not configurable.

    I've seen many cases where people attempt to "solve" the these kind of issues by increasing values.. which is way of compensating for poorly designed queries or exceeding the reasonable limit of how much data can be returned - remember the impact on of the End User experience - its best to optimize what you can and have fast loading Records and Tasks..



    The best and recommended approach is to only bring back what is actually needed - or only what is displayed use batching/pagination to your advantage. If you are finding the database query is very slow/not completing, an alternative approach is to create a "view" at the database level to reduce the returned results.

    For best Appian database practices, please see
    forum.appian.com/.../Database_Performance_Best_Practices.html
Reply
  • Be mindful that if you increase the default "conf.data.query.timeout" and"query.memory.limit", you increase the risk of having long running queries that Application Users perceive the Application to be 'frozen' or broken... Please look at redesigning or optimizing your query before changing any settings, and note that for Appian Cloud, these settings are locked down/not configurable.

    I've seen many cases where people attempt to "solve" the these kind of issues by increasing values.. which is way of compensating for poorly designed queries or exceeding the reasonable limit of how much data can be returned - remember the impact on of the End User experience - its best to optimize what you can and have fast loading Records and Tasks..



    The best and recommended approach is to only bring back what is actually needed - or only what is displayed use batching/pagination to your advantage. If you are finding the database query is very slow/not completing, an alternative approach is to create a "view" at the database level to reduce the returned results.

    For best Appian database practices, please see
    forum.appian.com/.../Database_Performance_Best_Practices.html
Children
No Data