Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAGt6o8kV=KgwMrPiSVcBie0Ugio8gA7=NZYALR6j=Z8zZJ1UCw@mail.gmail.com>
References: <CAGt6o8mTZqhd1SzwnzY4yy8PD-YaVK3RScHv0=o+qbwF2QXhjw@mail.gmail.com>
 <CA+eZwrHffDk=E-F170cPOXZpZHn0=qanmxMF3uYCzoe-9mR3aQ@mail.gmail.com>
 <CA+0=VoVk0ar3m_Y3+d9-Q0F0gi4CsSoJqd4JNSgSgg2aAcaSHA@mail.gmail.com>
 <dba8b535-d70c-4f9b-a5ef-3258dd0d02ea@misys.com> <CAGt6o8m4tAbTXLCS389cR_MGdysrcVondLyGNhJ8m_eg4jYMKg@mail.gmail.com>
 <CAGt6o8nUaMQ9VXdTrCDxkpoNZW4xMh6xJrZxWpnE6ff7EmeH4A@mail.gmail.com> <CAGt6o8kV=KgwMrPiSVcBie0Ugio8gA7=NZYALR6j=Z8zZJ1UCw@mail.gmail.com>
From: Sergey Kozlov <skozlov@gridgain.com>
Date: Mon, 24 Oct 2016 11:47:48 +0300
Message-ID: <CAMbfdjbAvGOdWQ-88D5-gT94rh+Saaa0ms5R1qWb4suav-dz_w@mail.gmail.com>
Subject: Re: Create separate thread pool for query execution
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a113ad9084d72dd053f98728b
archived-at: Mon, 24 Oct 2016 08:47:54 -0000

--001a113ad9084d72dd053f98728b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 =D0=BE=D0=BA=D1=82. 2016 =D0=B3. 8:57 =D0=BF=D0=BE=D0=BB=D1=8C=D0=B7=
=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Gilles, Romain" <
> romain.gilles@misys.com>
> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
>
> 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=C3=A9: 23 oct. 2016 23:00
> =C3=80: 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 f=
or
> any purpose, nor disclose its contents to any other person. This email do=
es
> 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 y=
ou
> are dealing.
>


--=20
Sergey Kozlov
GridGain Systems
www.gridgain.com

--001a113ad9084d72dd053f98728b--