Skip to main content

Production Java Profilers

I have been looking at java profiling tools. Mostly focusing on the following vendors:

  1. Precise – Good on java, Superb on the database, no RUM capability
    1. Would make a good tool for us, to help upgrade our current toolset of Idera SQLdm (which is a great product as well, but more limited).
  2. Dynatrace – Great on java, no DB, Superb RUM capability
    1. Coradiant brought me into this tool, which I had discounted due to a previous bad experience (about 2 years ago) when the product was very new into the .NET space. Product has a lot of similarities to the way that the Identify Appsight works, where you export a file and the developers open the file and do the deeper analysis.
    2. I also see they just announced the partnership today here : http://www.prweb.com/releases/Performance_Management/solution/prweb2464644.htm
  3. Wily – Best on java, no DB, not sure on RUM
    1. Put together a great deal for us, but I'm not sure how well the RUM products work, since they are new to the game.
    2. Not sure I want to give up my Coradiant…
  4. HP Diagnostics – Good on java, no DB, no RUM
    1. Best pricing, since we already do business with them, but I didn't see a lot of advancements in the tool since HP purchased them.

So that's the current project, along with a new helpdesk/bugtracking system (JIRA) we are building. We are also doing some additional work on our SEO. That sums it up other than that just the standard engineering work, support, and smaller projects.

Comments

Bryan Burwick said…
Ever look into Compuware's Vantage Analyzer for Java and .NET?

Give it a shot.
http://www.compuware.com/solutions/java_and_dotnet_performance.asp

I'd love to know your thoughts.

By the way, I'm a solution consultant for Compuware, out of Atlanta. I focus on End User Experience Monitoring, which has a cool integration for J2EE and .NET monitoring. We can determine what methods are running on the app server when a user experiences a slow running page due to server performance. I ran across your blog a few months ago when doing some research on ITSM methodology. I've been following your blogs through Google Reader.

If you want to get a copy to try out, let me know.
Unknown said…
Yeah I have seen the compuware stuff, its just a lot more expensive, and I don't have any other compuware in house here, so it makes more sense for me to go with Precise, Coradiant, or HP.
Anonymous said…
Wily and Dynatrace are both great products by nearly all accounts. But, take a close look at their overhead and whether you can afford that in a production setting. Ultimately, all of these tools do the same thing, in nearly the same way, but the ability to throttle the amount of overhead is what makes other tools on your list really shine.

Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, m aybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments. The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off component

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging): http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&postid=1171255 (registration is free) when HTTP_REQUEST { # Check if there is a JSESSIONID cookie if {[HTTP::cookie "JSESSIONID"] ne ""}{ # Persist off of the cookie value with a timeout of 2 hours (7200 seconds) p