Hi
@Sumit Srivastava,
About your first question:
As you can read in those threads (which focuses mainly on GPU execution, but in this case is the same)
https://community.omnisci.com/communities/community-home/digestviewer/viewthread?MessageKey=37e0a305-bb96-49f9-a88d-f7a53f36873e&CommunityKey=d06df790-8ca4-4e54-91a0-244af0228ddc&tab=digestviewer#bm37e0a305-bb96-49f9-a88d-f7a53f36873e
https://community.omnisci.com/communities/community-home/digestviewer/viewthread?MessageKey=2b17ccd0-d31b-4423-ab0b-20134ed708e4&CommunityKey=d06df790-8ca4-4e54-91a0-244af0228ddc&tab=digestviewer#bm2b17ccd0-d31b-4423-ab0b-20134ed708e4 OmniSci query execution is almost serial avoiding locking to maximize the usage of hardware resources, so there isn't any parameter to change the present behavior.
As you can read in the first link, you can set-up multiple omnisci instances with the same data with a load-balancer.
About the second question, as a workaround, you can turn on the dynamic watchdog turning on the
enable-dynamic-watchdog
(it will stop any query exceeding
dynamic-watchdog-time-limit
that default to 10000ms) and optimizing the offendings statements.
If you have a problematic query we will be happy to assist you to optimize statements and/or schemas to run better on the omnisci database.
Original Message:
Sent: 11-25-2019 10:59
From: Sumit Srivastava
Subject: How to run multiple Queries in Parallel
Query 1
Please let us know if any specific configuration required if would like to run multiple queries in parallel (CPU Version).
Query 2
How to abort any query in between. We have observed that query abort takes lot of time.
#Core