On 04/18/2013 09:32 PM, Liran Zelkha wrote: > Hi oVirt Board Members, > > We are starting a process of optimizing the Ovirt Engine code for > performance. To accomplish that, we need a Java Profiler. Many solutions > exist in the market, some of them are open source. However, for our > process, we need to have the following functionality from the profiler: > > * CPU profiling > o See the application Hot Spots - meaning which method takes the > longest to run, and how many times each method is run. > * Memory profiling. > o See the biggest objects that exist in the Engine heap, and who > created them. > * Database profiling. > o See the queries that are being sent to the database, how many > times they are executed, and the average execution duration. > * Thread profiling. > o Status of the system threads. > > These capabilities are covered by commercial profilers. One of them is > called JProfiler > (http://www.ej-technologies.com/products/jprofiler/overview.html). > The company that manufactures JProfiler offers a solution for open > source projects, allowing them to use JProfiler licenses for free, in > exchange for posting the JProfiler logo on the open source project site. > (See here <http://roq-messaging.org/> for an example) > > My question is whether you'll allow such posting on the Ovirt web > site, so that the Engine team can use JProfiler to improve Ovirt's > Engine performance. > > Thanks, > Liran Zelkha > > > _______________________________________________ > Board mailing list > Board(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/board > no replies, so i assume no one objects to this? _______________________________________________ Board mailing list Board(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/board

Hi all I have searched for open alternatives, but they do not provide full view of the application, as is needed in the profiling session of the engine we are conducting. The only alternative I can see is buy JProfiler licenses (or any other commercial profiler) and let internal RedHat team members use it when profiling. Please advise. ----- Original Message ----- From: "Jon Benedict" <Jon.Benedict(a)netapp.com&gt; To: "Itamar Heim" <iheim(a)redhat.com&gt;, "Liran Zelkha" <lzelkha(a)redhat.com&gt; Cc: board(a)ovirt.org Sent: Tuesday, May 14, 2013 6:12:40 PM Subject: Re: JProfiler I have no issue with this.

Hi Liran, It appears I am alone in having concerns about this so I would go ahead and request the project license as you proposed.

Thanks, Dave. On 06/25/2013 12:42 PM, Liran Zelkha wrote: > Hi all > > I have searched for open alternatives, but they do not provide full view of the application, as is needed in the profiling session of the engine we are conducting. > The only alternative I can see is buy JProfiler licenses (or any other commercial profiler) and let internal RedHat team members use it when profiling. > Please advise. > > ----- Original Message ----- > From: "Jon Benedict" <Jon.Benedict(a)netapp.com&gt; > To: "Itamar Heim" <iheim(a)redhat.com&gt;, "Liran Zelkha" <lzelkha(a)redhat.com&gt; > Cc: board(a)ovirt.org > Sent: Tuesday, May 14, 2013 6:12:40 PM > Subject: Re: JProfiler > > I have no issue with this. >

On 07/02/2013 02:33 AM, Dave Neary wrote: > Hi Liran, > > It appears I am alone in having concerns about this so I would go ahead > and request the project license as you proposed. FWIW, you can *always* figure I have concern about using non-FLOSS tools in an open source project. I like learning from history and past mistakes. Bottom line is, if people like us (and our engineering and product managers) don't step up to the line to deliver open solutions for our development needs, then we continue to fall behind closed-but-ready-today solutions in the drive toward deliverable dates. Every decision to purchase a closed solution instead of writing or fixing an open solution hurts the entire ecosystem. It's behavior we can expect at the corporate layer, but it shouldn't push its way up to the community project layer.

- Karsten > Thanks, > Dave. > > On 06/25/2013 12:42 PM, Liran Zelkha wrote: >> Hi all >> >> I have searched for open alternatives, but they do not provide full view of the application, as is needed in the profiling session of the engine we are conducting. >> The only alternative I can see is buy JProfiler licenses (or any other commercial profiler) and let internal RedHat team members use it when profiling. >> Please advise. >> >> ----- Original Message ----- >> From: "Jon Benedict" <Jon.Benedict(a)netapp.com&gt; >> To: "Itamar Heim" <iheim(a)redhat.com&gt;, "Liran Zelkha" <lzelkha(a)redhat.com&gt; >> Cc: board(a)ovirt.org >> Sent: Tuesday, May 14, 2013 6:12:40 PM >> Subject: Re: JProfiler >> >> I have no issue with this. >> > _______________________________________________ Board mailing list Board(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/board

On 04/18/2013 09:32 PM, Liran Zelkha wrote: > These capabilities are covered by commercial profilers. One of them is > called JProfiler > (http://www.ej-technologies.com/products/jprofiler/overview.html). > The company that manufactures JProfiler offers a solution for open > source projects, allowing them to use JProfiler licenses for free, in > exchange for posting the JProfiler logo on the open source project site. > (See here <http://roq-messaging.org/> for an example) > > My question is whether you'll allow such posting on the Ovirt web > site, so that the Engine team can use JProfiler to improve Ovirt's > Engine performance. no replies, so i assume no one objects to this?

Hi, On 05/12/2013 04:00 PM, Itamar Heim wrote: > On 04/18/2013 09:32 PM, Liran Zelkha wrote: >> These capabilities are covered by commercial profilers. One of them is >> called JProfiler >> (http://www.ej-technologies.com/products/jprofiler/overview.html). >> The company that manufactures JProfiler offers a solution for open >> source projects, allowing them to use JProfiler licenses for free, in >> exchange for posting the JProfiler logo on the open source project site. >> (See here <http://roq-messaging.org/> for an example) >> >> My question is whether you'll allow such posting on the Ovirt web >> site, so that the Engine team can use JProfiler to improve Ovirt's >> Engine performance. > > no replies, so i assume no one objects to this? I have no opposition to oVirt developers using JProfiler themselves, but I would not like to see it become a key piece of the project's infrastructure, because it is not open source. I also do not like the idea of promoting JProfiler, a proprietary tool, on the oVirt website. However, if the board members decide that this is appropriate, then we can do this.