We are using LargeMemoryPolicy (from public Store database) since our
application uses a lot of memory.
In 7.3.1 I notice that using LargeMemoryPolicy ensures that
VisualWorks allocates 40 MB chunks from the OS (Windows XP) whenever
memory needs to grow. This is in line with the description on the
package:
“ The policy (…) allocates chunks of RAM in 40 MB chunks (by default)
instead of 1 MB chunks to prevent growth thrashing.”
However, in VisualWorks 7.6, it seems like setting
preferredGrowthIncrement have no effect. I can allocate a small amount
of memory, and VisualWorks will immediately allocate more from the OS.
Did something change to the usage of “preferredGrowthIncrement”
between 7.3.1 and 7.6? I realize it is only a “preferred” amount, but
now it seems like this value is never used. This does not cause any
problems as far as I know, but an explanation would be good anyway.
Maybe Cincom could provided an updated memory policy tuned for the
current release?
I tested this using inspectors on ByteArray new: 1024 * 1024* 10
Kind regards
Runar
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
