Commandline tool to release cachememory

Which "Robert" are you referring to?

Please include context. Real, proper newsreaders make it easy to comply with netiquette rules about including appropriate context. Unfortunately, It is reported that Google makes it difficult. I don't have the details available quickly, but instructions have been posted frequently about how to force Google to let you include proper context.

It should be sufficient to show the developers the output of "ps augx grep $commandname" (with obvious subsbreastution) to show them their memory use is increasing.

Please be aware, though, that a Java virtual machine has its own memory management stuff not entirely under control of the application developer. If the JVM doesn't do garbage collection frequently enough, memory use can get large. It is often difficult for an application programmer to know when are good times to force garbage collection because of the CPU time it consumes and the resulting delay it causes to the user.

When you kill a process, the RAM allocated exclusively for that process is released and becomes completely free. That won't free up any cached disk blocks, and that recently freed RAM may later be occupied with other stuff.

-- Robert Riches (Yes, that is one of my email addresses.)