This BiblioTECH TechNote discusses the use of dynamic memory when running a BiblioTECH Server in a Hyper-V based virtual machine.
Microsoft Server includes the ability to allocate memory to Hyper-V based virtual machines both statically and dynamically.
Refer to this TechNet article for details about Hyper-V memory allocation.
On top of the memory required by the operating system, memory consumed by all services and any running applications, a BiblioTECH server will make three types of demands on memory
Base memory ...
During start up, the BiblioTECH server will build ‘in-memory’ lists. These will need memory to roughly the size of your database plus around 10%.
Once the server has started, while there may be minor variations, this memory allocation is effectively fixed in size.
Transaction memory ...
During normal operations, while processing client requests, additional memory needs to be allocated. This memory is consumed on demand and then released. Note : there could be several such transactions occurring at the same time.
Server Tasks memory ...
At various times throughout the day, a BiblioTECH server will perform server-based tasks (sending emails, backups, etc.). These can require the allocation of significant amounts of additional memory for each task.
Memory Usage and Performance
If memory is allocated in Hyper-V as static, then the memory will be available on demand – no issues.
However, if memory allocation is part static and part dynamic, a number of potential issues could arise ...
Allocation of dynamic memory is not instantaneous - there must be a delay (however small)
This may have an impact on the responsiveness of the system.
Over-Commitment of Memory
In situations where there are multiple virtual machines running on the same host computer, there is a temptation to over-commit the memory assigned to those virtual machines. This can be a good solution in that expensive server resources are utilised effectively.
However, each of the virtual machines running on the same host computer will make their own demands on memory. There is a chance that when the BiblioTECH server makes a memory allocation request, there will not be enough memory available. If this did occur, there would be a performance hit to BiblioTECH (possibly severe).
The allocation of virtual machine resources (esp. CPUs & Memory) from the host computer's pool of resources is something that requires careful tuning.
Each scenario is different and the requirments of a VM needs to be considered both for its own needs and for the impact on other VMs on the same host computer.
If you decide to utilise dynamic memory, you will need to tune the various parameters. As an initial starting point, try the following settings
Start Up = 2GB (ie. 2GB of static memory)
Maximum = 4GB (ie. 2GB of additional dynamic memory)
buffer = 30% (ie. hold a reasonably sized chunck of memory available for this VM)
priority = 70% (ie. give the BiblioTECH VM a higher then average priority)