Our product currently use SA on Linux OS. Since SA we are trying check and use intra-query parallelism mechanism. As known MAX_QUERY_TASKS option by default is set to 0 (maximum level of parallelism). In our experience we didn't see results of intra-query parallelism furthemore some of queries have encountered with endless loop processing or drop connection problems. Due these problems we set this option to 1 (prevent intra-query parallelism using). In last EBF's readme files we found fixes related to parallelism. For some tests we set MAX_QUERY_TASKS back to N/2 (where N count of logical processors) and saw in top output that realy were used N/2 processors. Our question - is the some recommendation to set MAX_QUERY_TASKS option regarding to number of logical processors; how last fixes have improved intra-query parallelism using

Thanks , Hanan Brener

asked 18 Dec '13, 12:52

HBrener's gravatar image

accept rate: 0%

Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 18 Dec '13, 12:52

question was seen: 925 times

last updated: 18 Dec '13, 12:52