Re: Cache operations performance metrics
Hello, Alexei. Thanks for the link on the ticket, lableled it with the IEP-35 label. What do you think about proposed metrics set? > 16 дек. 2019 г., в 10:29, Alexei Scherbakov > написал(а): > > Nikolay, > > What about batch operations? > > For messages processing the ticket does exist and even has an > implementation from before new metrics API times [1] > > [1] https://issues.apache.org/jira/browse/IGNITE-10418 > > пн, 16 дек. 2019 г. в 10:12, Николай Ижиков : > >> Hello, Igniters. >> >> I want to provide the user answers to the following question: "How cache >> API operations perform?" >> It seems, we need to implements metrics for basic cache API operations >> like get, put, remove for it. >> >> I think we should provide the following metrics: >> >> * `get`, `put`, `remove` time histograms. Measured for API calls on the >> caller node side. >>Implemented in [1], commit [2]. >> >> * `commit`, `rollback` time histograms. Measured for API calls on the >> caller node side [3]. >> >> * histograms that measure the time of processing `get`, `put`, `remove`, >> `commit`, `rollback` messages on affinity nodes(primary and backups). >>Ticket doesn't exist for it. >> >> What do you think? >> >> [1] https://issues.apache.org/jira/browse/IGNITE-12219 >> [2] >> https://github.com/apache/ignite/commit/e66bbef97b2cef73a533ce8a506ec479852cb364 >> [3] https://issues.apache.org/jira/browse/IGNITE-12450 >> > > > -- > > Best regards, > Alexei Scherbakov
Re: joining
Hello Dmitriy , Thanks for your clarification, definitely our employee will contribute with riEquaiton.com official mail id. Thanks, Prashant Rahulkar. On Sat, 14 Dec 2019 at 18:34, Dmitriy Pavlov wrote: > Hi Prashant, > > Thank you for your interest in Apache Ignite. And I hope the Ignite > community would be glad to work with new contributors. > > Just one note: A company can not contribute to an Apache project, but your > employee(s) can contribute as an individual. Similar is true for > management, an employee can be a member of PMC, but the project is managed > not by companies but only by the project management committee. > > Sincerely, > Dmitriy Pavlov > > сб, 14 дек. 2019 г. в 05:27, Prashant Rahulkar >: > > > Hello Everyone, > > I have started software firm in India, with complete motivation to focus > on > > open source technologies, so as a part of company policy we will star to > > contribute in this project with our company name. > > > > > > Thanks, > > PrashantR. > > > -- ~ Rahul
Re: Cache operations performance metrics
Nikolay, What about batch operations? For messages processing the ticket does exist and even has an implementation from before new metrics API times [1] [1] https://issues.apache.org/jira/browse/IGNITE-10418 пн, 16 дек. 2019 г. в 10:12, Николай Ижиков : > Hello, Igniters. > > I want to provide the user answers to the following question: "How cache > API operations perform?" > It seems, we need to implements metrics for basic cache API operations > like get, put, remove for it. > > I think we should provide the following metrics: > > * `get`, `put`, `remove` time histograms. Measured for API calls on the > caller node side. > Implemented in [1], commit [2]. > > * `commit`, `rollback` time histograms. Measured for API calls on the > caller node side [3]. > > * histograms that measure the time of processing `get`, `put`, `remove`, > `commit`, `rollback` messages on affinity nodes(primary and backups). > Ticket doesn't exist for it. > > What do you think? > > [1] https://issues.apache.org/jira/browse/IGNITE-12219 > [2] > https://github.com/apache/ignite/commit/e66bbef97b2cef73a533ce8a506ec479852cb364 > [3] https://issues.apache.org/jira/browse/IGNITE-12450 > -- Best regards, Alexei Scherbakov
Cache operations performance metrics
Hello, Igniters. I want to provide the user answers to the following question: "How cache API operations perform?" It seems, we need to implements metrics for basic cache API operations like get, put, remove for it. I think we should provide the following metrics: * `get`, `put`, `remove` time histograms. Measured for API calls on the caller node side. Implemented in [1], commit [2]. * `commit`, `rollback` time histograms. Measured for API calls on the caller node side [3]. * histograms that measure the time of processing `get`, `put`, `remove`, `commit`, `rollback` messages on affinity nodes(primary and backups). Ticket doesn't exist for it. What do you think? [1] https://issues.apache.org/jira/browse/IGNITE-12219 [2] https://github.com/apache/ignite/commit/e66bbef97b2cef73a533ce8a506ec479852cb364 [3] https://issues.apache.org/jira/browse/IGNITE-12450
Cache 6 suite is broken
Hi, I noticied that Cache 6 suite finishes badly (exit code 137) almost everytime [1] on master. It started recently. A problematic test inside is IgniteCache150ClientsTest. I made some attempts to fix the test (including reverting recent commits), but had no luck. And a hard part here is that I do not know whether the issue was caused by code changes or it is infrastructural one. My best attempt was increasing NetworkTimeout in test IgniteConfiguration [2]. After that the suite was able to finish, but IgniteCache150ClientsTest failed. Also, the problematic test seems so flaky, there are many failures in history. Do not have any really good solution in my mind. I see following options: 1. Use workaround in PR [2]. 2. Ignore test and dig deeper in scope of a separate ticket. What do you think? [1] https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Cache6?branch=%3Cdefault%3E=overview [2] https://github.com/apache/ignite/pull/7142/files -- Best regards, Ivan Pavlukhin
