Dear All,
Its after a long time, i am posting an article. Now a days i am very busy with my personal priorities which made me bit lazy in posting any articles.
While doing some research on an open source java profiler, i found this tool to be a best suitable one available in the market which has not become so popular. For many reasons i became a big fan of this tool as its really easy to configure this profiler on an any application server that supports java, I have tested this profiler on apache-tomcat and jboss on both windows as well as Linux and am successful in configuring sample application and profile the application. The information this tool provides is really comprehensive and there needs a minimal effort for any layman in obtaining the statistics related to the application like any other java profiler does, also another good thing I liked about this tool is it also provides some useful database related statistics such as poor performing queries, database query failures, database contention failure or slowness. Another good thing I love about this tool is, it has very minimal overhead on the application; I can say ~1% which is very less for any java profiling tool. I am currently planning to work on an open source application “Open KM” which is a document management system application and has all the features that a commercial application and can deployed on jboss by putting some load on the system and test it by tweaking the application and database by varying various key performance parameters that will effect any system and see what best this tool can provide us.
For more information please go through this link
I will share my experiences on the tool very soon.
Friday, February 19, 2010
Wednesday, October 28, 2009
Open Source Java Profiler
Hello Friends,
For those who are interested in Open Source Java Profiling tool.
Introduction
Jensor is a light-weight, low-overhead Java profiler written entirely in Java. Jensor is built on ByteCode Instrumentation (BCI) technology. Jensor provides innovative analysis techniques that help to detect and eliminate bottlenecks in Java applications. More interesting modules are as follows
* Tagging Engine
Allows breakup of data by user-defined tags. Tags can be created to view a business or technical or both perspectives. Tagging Engine thus provides for Business as well as Technical analysis based on the same underlying data.
* JVM Replay
Provides animated display of events that occured in the JVM. The replay thus creates a time and space perspective of methods executed in the JVM. This feature is useful in debugging reliability of Java applications.
* Pattern Analysis
Jensor discovers method call patterns based on the call graph sequence. Optimizing a pattern as opposed to a method provides cascading performance advantages across entire JVM.
http://jensor.sourceforge.net/
For those who are interested in Open Source Java Profiling tool.
Introduction
Jensor is a light-weight, low-overhead Java profiler written entirely in Java. Jensor is built on ByteCode Instrumentation (BCI) technology. Jensor provides innovative analysis techniques that help to detect and eliminate bottlenecks in Java applications. More interesting modules are as follows
* Tagging Engine
Allows breakup of data by user-defined tags. Tags can be created to view a business or technical or both perspectives. Tagging Engine thus provides for Business as well as Technical analysis based on the same underlying data.
* JVM Replay
Provides animated display of events that occured in the JVM. The replay thus creates a time and space perspective of methods executed in the JVM. This feature is useful in debugging reliability of Java applications.
* Pattern Analysis
Jensor discovers method call patterns based on the call graph sequence. Optimizing a pattern as opposed to a method provides cascading performance advantages across entire JVM.
http://jensor.sourceforge.net/
Open Source Network Profiler
Hello Friends,
Hope many of you might know about this network profiler which is open source tool developed by TCS Performance Engineering Research Center.
Introductory Information
WANem is a Wide Area Network Emulator, meant to provide a real experience of a Wide Area Network/Internet, during application development / testing over a LAN environment. Typically application developers develop applications on a LAN while the intended purpose for the same could be, clients accessing the same over the WAN or even the Internet. WANem thus allows the application development team to setup a transparent application gateway which can be used to simulate WAN characteristics like Network delay, Packet loss, Packet corruption, Disconnections, Packet re-ordering, Jitter, etc. WANem can be used to simulate Wide Area Network conditions for Data/Voice traffic and is released under the widely acceptable GPL v2 license. WANem thus provides emulation of Wide Area Network characteristics and thus allows data/voice applications to be tested in a realistic WAN environment before they are moved into production at an affordable cost. WANem is built on top of other FLOSS[Free Libre and OpenSource] components and like other intelligent FLOSS projects has chosen not to re-invent the wheel as much as possible.
For more details....please go through
http://wanem.sourceforge.net/
Hope many of you might know about this network profiler which is open source tool developed by TCS Performance Engineering Research Center.
Introductory Information
WANem is a Wide Area Network Emulator, meant to provide a real experience of a Wide Area Network/Internet, during application development / testing over a LAN environment. Typically application developers develop applications on a LAN while the intended purpose for the same could be, clients accessing the same over the WAN or even the Internet. WANem thus allows the application development team to setup a transparent application gateway which can be used to simulate WAN characteristics like Network delay, Packet loss, Packet corruption, Disconnections, Packet re-ordering, Jitter, etc. WANem can be used to simulate Wide Area Network conditions for Data/Voice traffic and is released under the widely acceptable GPL v2 license. WANem thus provides emulation of Wide Area Network characteristics and thus allows data/voice applications to be tested in a realistic WAN environment before they are moved into production at an affordable cost. WANem is built on top of other FLOSS[Free Libre and OpenSource] components and like other intelligent FLOSS projects has chosen not to re-invent the wheel as much as possible.
For more details....please go through
http://wanem.sourceforge.net/
Monday, September 7, 2009
HTTP 1.1 : Caching in HTTP
Hello Friends,
I found an article on HTTP Caching which seems to be useful. I have copied some portion of the article for your reference.
HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches. The HTTP/1.1 protocol includes a number of elements intended to make caching work as well as possible. Because these elements are inextricable from other aspects of the protocol, and because they interact with each other, it is useful to describe the basic caching design of HTTP separately from the detailed descriptions of methods, headers, response codes, etc.
Caching would be useless if it did not significantly improve performance. The goal of caching in HTTP/1.1 is to eliminate the need to send requests in many cases, and to eliminate the need to send full responses in many other cases. The former reduces the number of network round-trips required for many operations; we use an "expiration" mechanism for this purpose (see section 13.2). The latter reduces network bandwidth requirements; we use a "validation" mechanism for this purpose (see section 13.3).
For more details, please go through this link
http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html
I found an article on HTTP Caching which seems to be useful. I have copied some portion of the article for your reference.
HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches. The HTTP/1.1 protocol includes a number of elements intended to make caching work as well as possible. Because these elements are inextricable from other aspects of the protocol, and because they interact with each other, it is useful to describe the basic caching design of HTTP separately from the detailed descriptions of methods, headers, response codes, etc.
Caching would be useless if it did not significantly improve performance. The goal of caching in HTTP/1.1 is to eliminate the need to send requests in many cases, and to eliminate the need to send full responses in many other cases. The former reduces the number of network round-trips required for many operations; we use an "expiration" mechanism for this purpose (see section 13.2). The latter reduces network bandwidth requirements; we use a "validation" mechanism for this purpose (see section 13.3).
For more details, please go through this link
http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html
Subscribe to:
Posts (Atom)