On Fri, 24 Jun 2005 10:49:29 -0700, Joel wrote:
> I have several examples of various aspects of icon running very slowly
> when the program has grown very large, say >2GB in size.
>
> This is unexpected because I am running it on a Compaq Tru64 system,
> which should be using 64bit words for memory addresses, but I suppose
> it's possible that icon itself is doing something less efficient with
> memory addressing.
Hmmm, an Icon program growing that big would have a large
number of items in the heap (and 'active'). Since GC works by
traversing all active heap items, I could see where that might
take a while...
If you force the heap size way up on start to avoid GCs does
it run faster? If it does, then my best guess is that it's
slower because there's a lot of data there. (If not, then
I don't have any ideas...)
|
