ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: Create separate thread pool for query execution
Date Mon, 24 Oct 2016 09:17:35 GMT
> As far as the query thread pool, how many threads should be in it by
> default? What happens is the query is run from compute task - will the
> execution be shifted from the public to the query thread pool?

Pool management should be the same as for other pools.

Remote executions should be executed in query pool. Local should run
synchronously.

--Yakov

2016-10-24 11:53 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:

> Sergey, I think we already have a general approach with 3 or 4 thread pools
> we have today.
>
> As far as the query thread pool, how many threads should be in it by
> default? What happens is the query is run from compute task - will the
> execution be shifted from the public to the query thread pool?
>
> D.
>
> On Mon, Oct 24, 2016 at 1:47 AM, Sergey Kozlov <skozlov@gridgain.com>
> wrote:
>
> > Hi
> >
> > It seems we need a set of dedicated pools for various purposes. Could we
> > design a general apporach for this like following:
> >  - define dedicated pools in the grid configuration
> >  - run a query/compute/etc in the particular pool
> >
> > On Mon, Oct 24, 2016 at 9:49 AM, Vladimir Ozerov <vozerov@gridgain.com>
> > wrote:
> >
> > > Romain,
> > > We do not pre-start threads in our pools on Ignite start. Moreover,
> idle
> > > threads are stopped after some timeout.
> > >
> > > 24 окт. 2016 г. 8:57 пользователь "Gilles, Romain" <
> > > romain.gilles@misys.com>
> > > написал:
> > >
> > > Hi igniters,
> > > I'm not against to create a thread pool for each features but I have
> some
> > > difficulty to minimize the number of threads required to start
> ignite...
> > If
> > > you add too many thread pools does this will not increase the number of
> > > threads at startup?
> > >
> > > Thanks.
> > >
> > > Romain
> > >
> > >
> > > ________________________________
> > > De: Dmitriy Setrakyan <dsetrakyan@apache.org>
> > > Envoyé: 23 oct. 2016 23:00
> > > À: dev@ignite.apache.org
> > > Objet: Re: Create separate thread pool for query execution
> > >
> > > How about long running compute? Do we need a separate thread pool for
> it
> > as
> > > well?
> > >
> > > On Sun, Oct 23, 2016 at 3:57 AM, Sergi Vladykin <
> > sergi.vladykin@gmail.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Sergi
> > > >
> > > > 2016-10-23 11:52 GMT+03:00 Vladimir Ozerov <vozerov@gridgain.com>:
> > > >
> > > > > Igniters,
> > > > >
> > > > > Currently if several long-running queries are submitted, it may
> stall
> > > all
> > > > > cache operations because all theads in the system pool will be busy
> > > with
> > > > > queries.
> > > > >
> > > > > I think it makes sense to move queries execution into separate
> > > dedicated
> > > > > thread pool. As we have timeouts for core pool threads now, it
> should
> > > not
> > > > > affect memory consumption or startup time anyhow. Thoughts?
> > > > >
> > > > > Vladimir.
> > > > >
> > > >
> > > "Misys" is the trade name of the Misys group of companies. This email
> and
> > > any attachments have been scanned for known viruses using multiple
> > > scanners. This email message is intended for the named recipient only.
> It
> > > may be privileged and/or confidential. If you are not the named
> recipient
> > > of this email please notify us immediately and do not copy it or use it
> > for
> > > any purpose, nor disclose its contents to any other person. This email
> > does
> > > not constitute the commencement of legal relations between you and
> Misys.
> > > Please refer to the executed contract between you and the relevant
> member
> > > of the Misys group for the identity of the contracting party with which
> > you
> > > are dealing.
> > >
> >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message