This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I've heard of people going to all ends of the earth to get more memory for a machine running WSAD, but I've never heard of anyone intentionally trying to limit the memory the tool would use.
Joined: Sep 19, 2006
Cameron good point! I am doing some benchmarking and trying to set some constraints on memory like setting the max heap size and what not and someone told me that I should also set this. If I go about doing it where can I find steps to do this from the command line?
You may have already found the answer. If not here is a little help.
-vmargs -Xmx256M For large-scale development you should modify your VM arguments to make more heap available. This example allows the Java heap to grow to 256 MB. This may not be enough for large projects.
THe above is from ibm developers guide redbook.
Another tip from my personal experience, minimising WSAD 5.x window also releases any unused memory by the tool. I have verified this from the CPU utilization/memory usages.
hope this helps...
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com