Dynamic Memory free memory driver locked improvments.
In our environment we have many machines setup using dynamic memory. It seems when we need to do 8GB startup memory for applications so they can register 8GB of memory and we set minimum memory lower say 1GB and our max memory to 8GB we end up with a machine using 7.5GB of Memory @ all times. The memory is being used by the driver locked portion of memory. I know this is as designed. But I have profiled the machine and see it never gets close to 7.5GB of memory on startup. So why does it act like it did and driver locking it for memory faults to start pulling from it. Now why this is an issue is certain Java Development applications end up thinking the memory is used and we cannot get java to heap. If we set our dynamic memory lower on startup like 4GB, min 1GB and max of 8GB we get memory working as designed. But this time not showing 7.5GB being used by the driver locking process. We actually see about 1GB being used and we can visually add all the totals up in process monitor and match the total. But then we end up with applications saying we don't have 8GB of memory. I have found others online with this complaint and they end up turning off dynamic memory. For these machines they are using maybe 3GB memory tops for 4 hours a day. Please improve how the driver locking works and appears within the guests that use larger amounts of startup memory.