them
> > > timing
> > > > out once out of every two or three runs. These kind of problems
> > > undermine
> > > > confidence in Ignite.
> > > >
> > > > Mike
> > > >
> > > >
> > > > -Origin
gt; confidence in Ignite.
> > >
> > > Mike
> > >
> > >
> > > -Original Message-
> > > From: Valentin Kulichenko [mailto:valentin.kuliche...@gmail.com]
> > > Sent: 22 May 2017 19:15
> > > To: dev@ignite.apache.org
> > &
ulichenko [mailto:valentin.kuliche...@gmail.com]
> > Sent: 22 May 2017 19:15
> > To: dev@ignite.apache.org
> > Subject: Re: Inefficient approach to executing remote SQL queries
> >
> > Hi Mike,
> >
> > Generally, establishing connections in parallel could make sens
ay 2017 19:15
> To: dev@ignite.apache.org
> Subject: Re: Inefficient approach to executing remote SQL queries
>
> Hi Mike,
>
> Generally, establishing connections in parallel could make sense, but note
> that in most this would be a minor optimization, because:
>
>- Un
to executing remote SQL queries
Hi Mike,
Generally, establishing connections in parallel could make sense, but note that
in most this would be a minor optimization, because:
- Under load connections are established once and then reused. If you
observe disconnections during application
Hi Mike,
Generally, establishing connections in parallel could make sense, but note
that in most this would be a minor optimization, because:
- Under load connections are established once and then reused. If you
observe disconnections during application lifetime under load, then
