Add a comment

 

Re: Is VM size an architectural smell?

It depends on the service you are offering... in an internet scale system, where storing data in the JVM is never a good idea, I'd say anything requiring more than 128MB heap is an architectural smell. A little off topic, I once inherited a service that had a "memory leak", and had to be restarted every day. So, I looked at the maximum heap size, it was 24GB. I changed it to 512MB, and the problem went away. The memory leak was that the JVM was never garbage collecting, but rather just increasing its heap size until the OS refused, and then it threw out of memory errors. Back to the topic, heap size I've found is often programmers giving it more "just to be safe".

Re: Is VM size an architectural smell?


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).