"The answer to the question, "what amount of system resources will be consumed", is the same as the answer to "how much hardware is needed for this application"."
"A statistical approach for identifying memory leaks can work well with low overhead, using two key metrics: the age of each object (number of garbage collections it has survived) and the generation count for each class (the number of different ages of all objects of that class). A high class generation count indicates that your application is continuing to allocate new objects of that class without letting go of references to older objects of that class, possibly indicating a memory leak."