Next question what's the max memory allocation recommended? I have it as 1024 just now. Is it wirth doubleing or even quadrupleing it?
hi Vinnie,
what you need is to assign VASL enough mem to run in RAM, w/o having to use the system pagefile (hard disk memory, also called scratch-disk or swap-file), 'cos Java performs really poorly when it starts using the pagefile.
Personally, I'm set at 384MB for both initial & max Java RAM, but I have the userpref "High-quality image scaling (requires more memory)?" checked OFF. If you've got this pref checked ON, there's no need for you to go past 512MB for initial/max RAM.
As best I can determine, VASL needs a certain amount of memory, which gets used up by several factors:
- javaw.exe uses a fixed amount,
- vassalengine uses a fixed amount,
- VASL uses a fixed amount,
- whatever Extensions (including VASL4.mdx) you've got use what they need,
- displaying a map requires what the map needs, which is greatly increased by checking the above-mentioned userpref ON (iirc, this pref caches the zoom-in/out map-views at start-up for faster access)
- the on-map ctrs & overlays need space, too.
So you've got the fixed amount req'd by Java/VASSAL/VASL,
the variable amount req'd by your loaded Extensions,
& the amount req'd by your savegame file, which will include its map(s), overlays, & counters.
IMO you're gonna need a rilly monster game in order to need more than 512MB for Java RAM. I say, set your memallocation at 512 (for hi-Q image scaling) or 384 (for non-hi-Q image scaling) w/ this statement:
<j2se version="1.5+" initial-heap-size="384m" max-heap-size="384m"/>
or
<j2se version="1.5+" initial-heap-size="512m" max-heap-size="512m"/>
Keep in mind that your box has a fixed amount of RAM, that some of this is req'd for normal system functions, and more will be needed depending on whatever else you've got running while playing VASL, such as Skype, or spreadsheets, or browser or CD-player or whatever.
Those initial/max-heap-size statements will 'reserve' the stated amount of RAM for VASL, provided that you've got at least that same amount available for allocation. So, if your box only has 512meg of RAM, it's pointless to specify heap-sizes of 512 or greater just for VASL.
The default allocation when VASL starts will be 64meg, this amount was enough under the prior VASLv5.7/VASSALv2.8 to run a 'standard' geo-board scenario, but won't be large enough to start VASSALv3.0, let alone run a game, before it exceeds 64meg.
At least 128meg is needed now, w/ more for hi-Q image-scaling and/or large or CG-size games to open in RAM.
This mem-allocation will live in the userprefs once VASSALv3.1 is released, & the vassalengineers have decreased the amount of mem needed for image-handling.
