Emmanuel Hugonnet's Library tagged → View Popular
JDbMonitor - Monitor JDBC Performance For Slow SQL Queries
JDbMonitor is a tool to monitor & analyse database performance for any Java application.
Easily determine your application's database performance and analyse problems down to specific SQL statement.
Un vrai build incremental dans Maven | Le blog des experts J2EE
Le module module-parent contient 2 sous-modules : module-api et module-impl.
Le module module-impl contient une classe ProcessImpl qui implemente l'interface Process définie dans module-api.
Nous lancons la commande "mvn install" sur le projet parent. Tout marche parfaitement. Nous modifions la signature de l'interface Process dans module-api sans répercuter les changements sur ProcessImpl de module-impl.
Nous re-lançons une installation du projet sur module-parent avec la commande "mvn install".
Le build se déroule correctement et les livrables module-api.jar et module-impl.jar sont installés dans le repository Maven. Comme les sources de module-impl n'ont pas été éditées, Maven ne le recompile pas, bien qu'il dépende d'un module modifié : module-api. L'état du projet est donc invalide dans le repository maven car au runtime, le problème d'implémentation de Process par ProcessImpl lèvera une exception.
Ce problème peut être résolu en forçant le "clean" avant chaque "install". Le build n'est alors plus incremental et pour la modification d'une simple classe, le rebuild est total. Dans de gros projets utilisant l'intégration continue, le coût d'un rebuild total est trop élevé.
High-performance Ajax with Tomcat Advanced I/O
Using Non-Blocking I/O (NIO) improves server performance drastically because of its efficient use of system resources (threads). The gain in performance is noticeable in Asynchronous JavaScript + XML (Ajax) applications with long polling mechanisms. It also lets you control system-resource usage on a server under pressure. This article explains how to optimize your server for performance during the handling of both Ajax and regular requests.
Java run-time monitoring, Part 3: Monitoring performance and availability of an application's ecosystem
The third and final installment in this series on run-time monitoring of Java™ applications focuses on strategies and techniques for monitoring the performance and availability of an application's supporting and dependent services. These include the underlying host operating system, the operational database, and messaging infrastructures. The article concludes with a discussion of performance data management issues and data reporting and visualization.
Java run-time monitoring, Part 1: Run-time performance and availability monitoring for Java systems
Run-time performance monitoring is critical to achieving and maintaining a well-performing system. In this article, the first in a three-part series, Nicholas Whitehead explains how to do low-level granular monitoring of Java™ performance efficiently. The data you generate can provide valuable insights into system operation and reveal constraints and influences that affect an environment's stability and performance.
Robust Java benchmarking, Part 2: Statistics and solutions
Program performance is always a concern, even in this era of high-performance hardware. This article, the second in a two-part series, covers the statistics of benchmarking and offers a framework you can use to benchmark Java™ code ranging from self-contained microbenchmarks to code that calls a full application.
-
Program performance is always a concern, even in this era of high-performance hardware. This article, the second in a two-part series, covers the statistics of benchmarking and offers a framework you can use to benchmark Java™ code ranging from self-contained microbenchmarks to code that calls a full application.
Robust Java benchmarking, Part 1: Issues
Program performance is always a concern, even in this era of high-performance hardware. This article, the first in a two-part series, guides you around the many pitfalls associated with benchmarking Java™ code. Part 2 covers the statistics of benchmarking and offers a framework for performing Java benchmarking. Because almost all new languages are virtual machine-based, the general principles the article describes have broad significance for the programming community at large.
http://www.cs.umd.edu/~pugh/java/memoryModel/jsr-133-faq.html
The Java Memory Model was an ambitious undertaking; it was the first time that a programming language specification attempted to incorporate a memory model which could provide consistent semantics for concurrency across a variety of architectures. Unfortunately, defining a memory model which is both consistent and intuitive proved far more difficult than expected. JSR 133 defines a new memory model for the Java language which fixes the flaws of the earlier memory model. In order to do this, the semantics of final and volatile needed to change.
The full semantics are available at http://www.cs.umd.edu/users/pugh/java/memoryModel, but the formal semantics are not for the timid. It is surprising, and sobering, to discover how complicated seemingly simple concepts like synchronization really are. Fortunately, you need not understand the details of the formal semantics -- the goal of JSR 133 was to create a set of formal semantics that provides an intuitive framework for how volatile, synchronized, and final work.
Java Virtual Machine Tuning under JVM 1.4.2
This page is intended to document some proposals and empirical data gathered while attempting to tune the JVM used for running web applications on CBC.ca’s Java servers.
Parallel and concurrent garbage collectors
The original generational collector was single threaded. A parallel collector was required, and since the young and old generation memory spaces are different in the way the objects residing in them are used, so are the collectors implemented for them.
Either You Succeed or Explain: Five ways for tracing Java execution
In this post, I will summarize the common methods for tracing the runtime execution. The tips and examples are assuming you're using Eclipse, but most of them can be achieved with other IDEs as well.
Java diagnostics, IBM style, Part 4: Extending the IBM Dump Analyzer for Java with analysis modules
This article wraps up this series on IBM diagnostic tooling for the Java platform by showing you how to build analyzers that will help you plumb the depths of your system dumps and fine-tune your Java code.
Java diagnostics, IBM style, Part 3: Diagnosing synchronization and locking problems with the Lock Analyzer for Java
This article introduces Lock Analyzer for Java, explains the architecture on which it is built, and provides some thoughts about the tool's future direction. It provides real-time lock monitoring on a running Java application.
Java diagnostics, IBM style, Part 2: Garbage collection with the Extensible Verbose Toolkit
The Extensible Verbose Toolkit is designed to help diagnose and analyze memory-related Java performance problems. This article explains how to obtain and use the toolkit and demonstrates how you can use it to quickly diagnose some common problems.
Java diagnostics, IBM style, Part 1: Introducing the IBM Dump Analyzer for Java
This article introduces the IBM Dump Analyzer for Java and provides some background information about the types of problems that the tool can diagnose. It explains the architecture and provides some thoughts about the future direction of the tool.
visualvm: Project Home Page
VisualVM is a tool that provides detailed information visually about Java applications while they are running. You can easily see information about multiple Java applications. Java applications are run by a Java Virtual Machine, or VM.
Tuning Garbage Collection with the 5.0 Java[tm] Virtual Machine
Tuning Garbage Collection with the 5.0 JavaTM Virtual Machine: memory model for Java
Java SE 6 HotSpot[tm] Virtual Machine Garbage Collection Tuning
Java SE 6 HotSpot[tm] Virtual Machine Garbage Collection Tuning: memory model for Java
Glassbox.com
Glassbox is a troubleshooting agent for Java applications that automatically
diagnoses common problems.
Home - Lambda Probe
Welcome to the home of Lambda Probe - the ultimate tool for monitoring and management of Apache Tomcat instance in real time. Lambda Probe will help you to visualise real time information about Tomcat instance via easy to use and friendly web interface.
Selected Tags
Related Tags
Sponsored Links
Top Contributors
Groups interested in performa...
-
Rails Performance Optimization
Items: 7 | Visits: 60
Created by: Avdi Grimm
-
Consistent Hashing
Items: 8 | Visits: 85
Created by: Arrix Z
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo
