memory_leaks
Get flash to fully experience Pearltrees
Choosing innodb_buffer_pool_size | MySQL Performance Blog
November 3, 2007 By Peter Zaitsev 39 Comments My last post about Innodb Performance Optimization got a lot of comments choosing proper innodb_buffer_pool_size and indeed I oversimplified things a bit too much, so let me write a bit better description. Innodb Buffer Pool is by far the most important option for Innodb Performance and it must be set correctly. I’ve seen a lot of clients which came through extreme sufferings leaving it at default value (8M). So if you have dedicated MySQL Box and you’re only using Innodb tables you will want to give all memory you do not need for other needs for Innodb Buffer Pool.
How to Fix Memory Leaks in Java Your pager hasn't been sleeping well. It periodically wakes you up in the middle of the night to tell you that your server is firing off "OutOfMemoryError" messages.
Wazi " Tutorials " How to Fix Memory Leaks in Java
November 2008 This document is a guide to help troubleshoot problems that might arise with applications that are developed using the release of Java Platform, Standard Edition 6 (JDK 6 release or Java SE 6 release). In particular, this guide addresses possible problems between the applications and the Java HotSpot virtual machine.
Troubleshooting Memory Leaks - Troubleshooting Guide for Java SE
Handling memory leaks in Java programs
How memory leaks manifest themselves in Java programs Most programmers know that one of the beauties of using a programming language such as Java is that they no longer have to worry about allocating and freeing memory. You simply create objects, and Java takes care of removing them when they are no longer needed by the application through a mechanism known as garbage collection.
Tuning Garbage Collection with the 5.0 Java[tm] Virtual Machine
Introduction The Java TM 2 Platform Standard Edition (J2SE TM platform) is used for a wide variety of applications from small applets on desktops to web services on large servers. In the J2SE platform version 1.4.2 there were four garbage collectors from which to choose but without an explicit choice by the user the serial garbage collector was always chosen.Nov 05 I spent far too much time on a stupid bug of my making. Part of my model had a simple One to Many relationship.
Watch out for Hibernate unsaved-value