Re: one point optimisation

Hi! Your talking about node ordering? What is the point of the ordering? How is it implemented? Thanks for the answering in advance! ср, 5 апр. 2017 г. в 15:14, Alexey Goncharuk : > This optimization does not work when near cache is enabled because we need > the same ordering on near nodes. You s

Re: one point optimisation

would like to add 1 phase optimisation isn't gonna work if write through is enabled. ср, 5 апр. 2017 г. в 15:23, Антон Чураев : > Maybe it will be useful to update the documentation? > > 2017-04-05 15:15 GMT+03:00 ALEKSEY KUZNETSOV : > > > Thank you for help! > > > > ср, 5 апр. 2017 г. в 15:14, A

Re: one point optimisation

Maybe it will be useful to update the documentation? 2017-04-05 15:15 GMT+03:00 ALEKSEY KUZNETSOV : > Thank you for help! > > ср, 5 апр. 2017 г. в 15:14, Alexey Goncharuk : > > > This optimization does not work when near cache is enabled because we > need > > the same ordering on near nodes. You

Re: one point optimisation

Thank you for help! ср, 5 апр. 2017 г. в 15:14, Alexey Goncharuk : > This optimization does not work when near cache is enabled because we need > the same ordering on near nodes. You should see the expected number of > messages with near cache disabled. > > 2017-04-05 15:09 GMT+03:00 ALEKSEY KUZN

Re: one point optimisation

This optimization does not work when near cache is enabled because we need the same ordering on near nodes. You should see the expected number of messages with near cache disabled. 2017-04-05 15:09 GMT+03:00 ALEKSEY KUZNETSOV : > yes > > ср, 5 апр. 2017 г. в 15:07, Alexey Goncharuk : > > > Do you

Re: one point optimisation

yes ср, 5 апр. 2017 г. в 15:07, Alexey Goncharuk : > Do you have a near cache enabled? > > 2017-04-05 15:00 GMT+03:00 ALEKSEY KUZNETSOV : > > > The test shows as follows: > > assertMessageCount(GridNearTxPrepareRequest.class, 1); > > assertMessageCount(GridDhtTxPrepareRequ

Re: one point optimisation

Do you have a near cache enabled? 2017-04-05 15:00 GMT+03:00 ALEKSEY KUZNETSOV : > The test shows as follows: > assertMessageCount(GridNearTxPrepareRequest.class, 1); > assertMessageCount(GridDhtTxPrepareRequest.class, 1); > assertMessageCount(GridDhtTxPrepareR

Re: one point optimisation

The test shows as follows: assertMessageCount(GridNearTxPrepareRequest.class, 1); assertMessageCount(GridDhtTxPrepareRequest.class, 1); assertMessageCount(GridDhtTxPrepareResponse.class, 1); assertMessageCount(GridNearTxPrepareResponse.class, 1);

Re: one point optimisation

Aleksey, Can you elaborate on which of the extra messages you observe? --AG 2017-04-04 14:17 GMT+03:00 ALEKSEY KUZNETSOV : > any thoughts on one phase commit realization ? > > пн, 3 апр. 2017 г. в 19:35, ALEKSEY KUZNETSOV : > > > I've attached test that prints messages exchange . Which shows us

Re: one point optimisation

any thoughts on one phase commit realization ? пн, 3 апр. 2017 г. в 19:35, ALEKSEY KUZNETSOV : > I've attached test that prints messages exchange . Which shows us that > there are more messages then you declared in article. Perhaps, > implementation has changed. > I created it on base of IgniteOn

Re: one point optimisation

I've attached test that prints messages exchange . Which shows us that there are more messages then you declared in article. Perhaps, implementation has changed. I created it on base of IgniteOnePhaseCommitNearSelfTest пн, 3 апр. 2017 г. в 19:03, Dmitriy Setrakyan : > Aleksey, > > The blog descri

Re: one point optimisation

Aleksey, The blog describes the 1-phase commit at a high level, but I am still curious about the differences you found. Can you share them here? D. On Mon, Apr 3, 2017 at 2:11 AM, ALEKSEY KUZNETSOV wrote: > Regarding IgniteOnePhaseCommitNearSelfTest test , ignite's one phase > optimisation wor

Re: one point optimisation

Regarding IgniteOnePhaseCommitNearSelfTest test , ignite's one phase optimisation works not as you said. I attached picture of message exchange. There are partial prepare phase exists, along with finish phase. пн, 3 апр. 2017 г. в 10:55, Christos Erotocritou : > As far as I know a partition is

Re: one point optimisation

As far as I know a partition is always allocated to a specific node and does not span nodes. Ignite has default 1024 partitions on start that are split equally across nodes. > On 3 Apr 2017, at 08:10, ALEKSEY KUZNETSOV wrote: > > in ur blog u texted belonging to the same partition is nessesar

Re: one point optimisation

in ur blog u texted belonging to the same partition is nessesary for 1 phase commit. But its not guarantee belonging to the same node. Partition may span many nodes вс, 2 Апр 2017 г., 13:46 ALEKSEY KUZNETSOV : > thank u ! > > пт, 31 Мар 2017 г., 21:06 Denis Magda : > > Here is a good blog post ab

Re: one point optimisation

thank u ! пт, 31 Мар 2017 г., 21:06 Denis Magda : > Here is a good blog post about 1phase commit impl in Ignite and its > advantages: > > http://gridgain.blogspot.com/2014/09/one-phase-commit-fast-transactions-for.html > < > http://gridgain.blogspot.com/2014/09/one-phase-commit-fast-transactions-

Re: one point optimisation

Here is a good blog post about 1phase commit impl in Ignite and its advantages: http://gridgain.blogspot.com/2014/09/one-phase-commit-fast-transactions-for.html Took a reference to it from there: https://apacheign

Re: one point optimisation

On Fri, Mar 31, 2017 at 9:25 AM, ALEKSEY KUZNETSOV wrote: > Igniters! What is the point of one phase optimisation? > Performance

one point optimisation

Igniters! What is the point of one phase optimisation? -- *Best Regards,* *Kuznetsov Aleksey*