Re: IEP-46 Thin client - Service invocation

2020-06-02 Thread Alex Plehanov
Alexey, Yes, I've got almost the same performance (the difference is about 1%). I think proxy creation has a relatively low cost compared to 2-4 network hops required to invoke the service method. More precisely: First approach: create a service proxy on server-side each time, when a service

Re: IEP-46 Thin client - Service invocation

2020-06-02 Thread Alexey Goncharuk
Alexey, Hello, > > I've benchmarked 1-operation approach vs 2-operations approach and > published benchmark results on IEP page [1]. It looks like performance > almost the same, so the single-operation approach should be implemented. > Do I understand correctly that you suggest to remote the

Re: IEP-46 Thin client - Service invocation

2020-06-02 Thread Alex Plehanov
Hello, I've benchmarked 1-operation approach vs 2-operations approach and published benchmark results on IEP page [1]. It looks like performance almost the same, so the single-operation approach should be implemented. One more question: do we need some parameter on the server-side to disable

Re: IEP-46 Thin client - Service invocation

2020-05-20 Thread Alex Plehanov
Pavel, I will try to benchmark by myself. Thank you. ср, 20 мая 2020 г. в 13:54, Pavel Tupitsyn : > Alex, > > Thank you, the IEP looks complete now. > > Are you going to do the comparison benchmark of 1-operation vs 2-operation > modes? > I can do that too, just want to avoid duplicate work. >

Re: IEP-46 Thin client - Service invocation

2020-05-20 Thread Pavel Tupitsyn
Alex, Thank you, the IEP looks complete now. Are you going to do the comparison benchmark of 1-operation vs 2-operation modes? I can do that too, just want to avoid duplicate work. On Wed, May 20, 2020 at 1:17 PM Alex Plehanov wrote: > Pavel, > > Yes, looks like we can get this information

Re: IEP-46 Thin client - Service invocation

2020-05-20 Thread Alex Plehanov
Pavel, Yes, looks like we can get this information from ServiceDescriptor. I've removed 'interface name' from requests in IEP. Thank you! ср, 20 мая 2020 г. в 12:58, Pavel Tupitsyn : > Alex, > > IEP looks good to me in general. > > One question: what is `Interface name` in the request? > As I

Re: IEP-46 Thin client - Service invocation

2020-05-20 Thread Pavel Tupitsyn
Alex, IEP looks good to me in general. One question: what is `Interface name` in the request? As I understand, service name is enough to retrieve ServiceDescriptor, and then we can get serviceClass from there. On Wed, May 20, 2020 at 12:42 PM Alex Plehanov wrote: > Pavel, > > I've moved

Re: IEP-46 Thin client - Service invocation

2020-05-20 Thread Alex Plehanov
Pavel, I've moved proposals from this thread to the IEP [1] and described changes to protocol, please have a look. [1] : https://cwiki.apache.org/confluence/display/IGNITE/IEP-46%3A+Thin+Client+Service+Invocation пн, 18 мая 2020 г. в 15:09, Pavel Tupitsyn : > Hi Alex, > > Thanks for starting

Re: IEP-46 Thin client - Service invocation

2020-05-18 Thread Pavel Tupitsyn
Hi Alex, Thanks for starting this thread. I've created the IEP some time ago but then got distracted by other things. My thoughts: *1. Create service proxy on each invoke request* Single client operation is a lot simpler to implement on both sides (client and server), so I would prefer this