Develop Update Server in Java

On Fri, 30 Oct 2009 13:22:01 -0700, Peter Duniho wrote:

.....snipped some very good points.....
>
> If it doesn't pre-allocate the heap, then having to specify the heap
> limit on startup is just dumb. (Which is no guarantee that it doesn't
> pre-allocate the heap, of course...)
>
I know of a couple of OSes with considerably better process execution
schedulers than any of the currently popular crop which use process
memory requirements as an input to their low level (millisecond level)
scheduler. If they are told how the process uses its memory (size of the
code, constants, stack and heap segments) this can be used to determine
the paging strategy for each region and to optimise the execution
strategy for the current process mix.

So, I think its sensible for the JVM to have the ability to specify heap
size regardless of whether a current OS chooses to use the information or
to ignore it: heap and stack size can't be determined at load time if
they aren't specified as JVM parameters.


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |

Martin Gregorie