Hi venkat, Yes we can. lets have a call today around 9.30 p.m
On Thu, Aug 4, 2016 at 9:34 AM, Venkat Raman <[email protected]> wrote: > Hi Isuru, > > Good morning. Yesterday night, I spoke with Kasun regarding the latest > update on bench-mark results. Even without any locking performance is not > good after concurrency of 5000. > > As you have done bench-mark till concurrency of 3000, we both would like > to do bench-marking on raw carbon-transport upto concurrency of 10,000 and > 1,00,000 requests so that we get an idea on this. > > How do we do that ? Will a simple response from engine suffice ? Can I > use LB to send simple response directly without doing any mediation ? > > > > > *Thanks,* > *Venkat.* > > On Thu, Aug 4, 2016 at 12:19 AM, Venkat Raman <[email protected]> > wrote: > >> Hi Isuru, >> >> Please find the attached bench-mark results. As discussed, I've >> disabled health-checking and removed synchronized block and used atomic >> Integer in one test and also did a test without any kind of lock or use of >> atomic integers. >> >> Throughput and latency results are positive. But, after concurrency >> level of 5000 it is not that good. So even If we use read-write lock or >> stamped lock, we will get performance little performance gain only. >> >> I feel that If we can do bench-mark with integration-server upto 10000 >> concurrent connections we'll get a better idea. Is that okay ? >> >> >> >> >> *Thanks,* >> *Venkat.* >> >> On Tue, Aug 2, 2016 at 9:39 PM, Venkat Raman <[email protected]> >> wrote: >> >>> Hi Isuru & Kasun, >>> >>> Please find the findings from today's code review. >>> >>> 1) Locking in getNextLBOutboundEndpoint() method in algorithm >>> implementation is causing over-head. We have to find a way to efficiently >>> handle communication between threads to reduce locking overhead. >>> >>> 2) Code repo freeze by August 15th for the sake of GSoC. If we can find >>> a way to overcome locking over-head before August 15th that changes will be >>> added to code repo. Otherwise it will be added after GSoC. >>> >>> 3) TPS, Latency and Memory graphs to be added. >>> >>> 4) Blog post and PDF documentation. >>> >>> >>> >>> >>> *Thanks,* >>> *Venkat.* >>> >>> On Mon, Aug 1, 2016 at 9:25 AM, Venkat Raman <[email protected]> >>> wrote: >>> >>>> Hi Isuru, >>>> >>>> Good morning. Please find 10th week's progress. >>>> >>>> 1) Had discussion with Kasun. >>>> 2) As suggested, did performance bench-marking using Netty BE, and it >>>> turns out that our LB is beating Nginx till concurrency level of 6000 after >>>> which it is not performing well. >>>> I've attached the results. >>>> >>>> I've started a new thread as Conversation arrangement is not good in >>>> previous one. >>>> >>>> It would be great if we can have a code review Isuru. Based on your >>>> feedback I'll be abe to make changes and we can do bench-marking again. >>>> Can we do it today 9:30 PM ? We have only 2 full weeks more. The last >>>> week will be for documentation. >>>> >>>> >>>> >>>> *Thanks,* >>>> *Venkat.* >>>> >>> >>> >> > -- Best Regards Isuru Ranawaka M: +94714629880 Blog : http://isurur.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
