Re: Hyracks Job Requirement Configuration

+ dev On 1/28/18 3:37 PM, Rana Alotaibi wrote: Hi all, I would like to make AsterixDB utilizes all available CPU cores (39) that I have for the following query: USE mimiciii; SET `compiler.parallelism` "39"; SET `compiler.sortmemory` "128MB"; SET `compiler.joinmemory` "265MB"; SELECT

Re: Hyracks Job Requirement Configuration

*- Do you see all cores being fully utilized during the query execution? * I have noticed only 6 cores were utilized *- How much time does the query take right now and how do you measure the query execution time? Do you wait for the result to be printed somewhere (e.g. in the browser)?* I'm

Re: Hyracks Job Requirement Configuration

If reloading the data isn’t too much trouble, the first thing I would do is recreate the instance with more partitions (e.g. partition per core or partition per 2 cores) and check the cores utilization. If this is the same dataset as the one in your previous email, you mentioned that it was

Re: Hyracks Job Requirement Configuration

I have few questions if you don’t mind: Do you see all cores being fully utilized during the query execution? How much time does the query take right now and how do you measure the query execution time? Do you wait for the result to be printed somewhere (e.g. in the browser)? You mentioned

Hyracks Job Requirement Configuration

Hi all, I would like to make AsterixDB utilizes all available CPU cores (39) that I have for the following query: USE mimiciii; SET `compiler.parallelism` "39"; SET `compiler.sortmemory` "128MB"; SET `compiler.joinmemory` "265MB"; SELECT P.SUBJECT_ID FROM LABITEMS I, PATIENTS P, P.ADMISSIONS

Re: Hyracks Job Requirement Configuration

Hi Rana, The memory used for query processing is automatically calculated as follows: JVM Max Memory - storage.buffercache.size - storage.memorycomponent.globalbudget The documentation defaults for these parameters are outdated. The default value for storage.buffercache.size is (JVM Max Memory

Re: Hyracks Job Requirement Configuration

Thanks Murtadha! The problem solved. However, increasing the number of cores didn't help to improve the performance of that query. On Sun, Jan 28, 2018 at 5:05 PM, Murtadha Hubail wrote: > Hi Rana, > > The memory used for query processing is automatically calculated as >