[nylug-talk] Free -m shows 300MB usage after upgrade to 1GB.

[Henning Follmann]

On Jan 2, 2008, at 12:33 PM, sixtyfourbeets wrote:

> This is by design.
> The kernel keeps as much as possible into buffer. Yes you could change
> that, but you shouldn't.
>
>
> Henning
>
> --------------------------------------------------------------------------------------------
>
> I guess I had it backwards.
>
> So why does Java suck up all that memory and then dips into the swap  
> space?
>
>

Here is my thinking about java (after I recently started a java based  
project after some time of non java development - which I now refer to  
as the good old times).
One obvious problem is that everything is sucked up in one virtual  
machine which is just one big bloated process from the perspective of  
the kernel. All management of library space and application space has  
to be handled by the JVM not the kernel anymore.

And then there is the obvious problem with the java community:  
everybody is high on pattern, OOD and OOP, so they tend to over- 
pattern and  over-class and make code non-obvious which as a  
consequence leads to more non-obvious code.
They like to reuse and are willing to learn and use whole new  
frameworks just because the need a simple FactoryClass (lets use  
spring then). They think its better to have code not only in java but  
also in xml ( and now they call it configuration) and love parameter  
files also. They think it make things flexible.

Java today is a memory hog because of the altered brains of most java  
developers.


Henning