while going through Vertica configuration parameters table, I found these two parameters
1. NewEEThread : Number of threads the EE will attempt to use for processing (per plan)
2. SortWorkerThreads : Controls the number of Sort worker threads; 0 disables background threads
According to description , I am a bit confused on where does this parameter come int picture while query execution.
Also, Is there any co-relation between NewEEThread and Plannedconcurrency from resource pools, I know plannedconcurrency can be set for different resource pool, but what part does NewEEThread do here ?
Also some more insights into both these paramters.
Thanks
NewEEThread vs Plannedconcurrency
Moderator: NorbertKrupa
Re: NewEEThread vs Plannedconcurrency
Hi!
[DELETED]
[DELETED]
Last edited by id10t on Wed May 06, 2015 4:41 pm, edited 1 time in total.
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: NewEEThread vs Plannedconcurrency
In the "Advanced Projection Design" course at the Vertica Big Data Conference the presenter said that Vertica uses the "Quicksort".
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Re: NewEEThread vs Plannedconcurrency
Hi!
[DELETED]
[DELETED]
Last edited by id10t on Wed May 06, 2015 4:41 pm, edited 1 time in total.
Re: NewEEThread vs Plannedconcurrency
There’s no need to ever touch NewEEThread. If you want to affect the number of threads/cores used by a query, these days you would use the EXECUTIONPARALLELISM setting for each resource pool.
—Sharon
—Sharon
Sharon Cutter
Vertica Consultant, Zazz Technologies LLC
Vertica Consultant, Zazz Technologies LLC