RE: Functions and memory usage

["Fabio Reis Cecin" <frcecin@...>]

Here's some material on the Java garbage collector(s) (there is more than one
and it seems that you can select wich one you want) :

http://java.sun.com/products/hotspot/whitepaper.html#5
http://developer.java.sun.com/developer/technicalArticles/Networking/HotSpot/

One of them uses the "train" algorythm, wich supposedly eliminates
undesirable 1-sec pauses when "mark-compact"-like garbage collection
would occur.

Another idea: have a couple of functions on the Lua API for the
programmer to know an estimate of how bad fragmentation is, and to
be able to force a full GC and full memory compaction. This could be
useful for the programmer to call, when the user "pauses the game",
or is detected to be away for the program, or when the game is
changing levels, etc.

Fabio

On 17 Oct 2002, at 9:17, John Mckenna wrote:

> >2. you should consider compacting or moving garbage collection
> >   techniques, which do have some drawbacks (in particular, real-time
> >   or interactive-time constraints may require tricky tradeoffs or
> >   tuning with such moving GCs).
> 
> You mean spend CPU time on something that's not directly related to
> the game?  Heresy! :-)
> 
> John
> -Virus scanned and cleared ok
> 
> Esta mensagem foi verificada pelo E-mail Protegido Terra.
> Scan engine: VirusScan / Atualizado em 16/10/2002 / Versão: 1.3.13
> Proteja o seu e-mail Terra: http://www.emailprotegido.terra.com.br/
> 


--
[]'s
Fábio R. Cecin
frcecin@terra.com.br