This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
Product Feedback Forum
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Community
- Product Feedback
- Elacticube build - Level of parallelism
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Hello,
How about having a better control over queries parallelism ?
My use case :
Elasticubes using 2 connections : DB1 / DB2
Currently, the parameter BaseTableMaxThreads (sets to 2 for us) controls how many queries can run in parallel, whatever the connection. During build, we frequently see situations where we have 1 query on DB1 and another one on DB2. Reducing the level of parallelism was necessary to limit contention on one connection but it would be fine to have 2 queries on DB1 and 2 queries on DB2 at the same time.
My proposal is the following : having a parameters to controls the level of parallelism per connection and not per build.
Thank you.
See more ideas labeled with:
