Byte value between 10 and 200. Specifies the percentage of available physical RAM to allocate to the CRC calculation process. The default value is 50 (%).
Using this property tells the toolkit what percentage of physical RAM to allocate to each 'chunk' of data read from the file being parsed by the CRC32File Method. Restricting data size in line with available physical RAM offers considerable speed advantages because we avoid the use of the swapfile (RAM written to much-slower hard disc).Setting this property brings with it no guarantee of the actual amount of RAM that the toolkit will use. There is a very small RAM overhead - as with all software - from the state variables needed, the lookup tables, and so on.
It is advisable to experiment with this setting (and please give us your feedback too). Setting this too high is likely to result in the user's system allocating more swap space, or swapping processes out, on a pre-emptive basis. Setting it to low may impact on performance. Overall, however, you should not be too concerned! By using physical RAM as far as possible, being table driven, and performing the checksum calculations in assembly language, CRC32 can't really go much faster than this without dedicated hardware.
A value in excess of 100 (%) allocate more memory to the byte array than the amount of physical RAM currently available. This just might be fast, what with system caching, the swapping out of other processes, etc., but most likely will not be. A value of more than 80% or so is not recommended, more than 100% at your peril!
This property value is used to calculate a 'maximum chunk size' once only per method call. The memory allotted is of course freed when the method is completed. The property is ignored by the CRC32File Method if the method is called with a MaxChunkSize argument.