Changes between Initial Version and Version 1 of Ticket #15195, comment 5
- Timestamp:
- Mar 8, 2016 5:34:10 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15195, comment 5
initial v1 3 3 I would rather check my assertion first and establish what actually is expected behaviour for VirtualBox. The is little that appears particularly relevant to memory in this fashion in the log anyway. What would be superior is to know what in the log related to the initialisation of memory management modes and to know how to have some basic output of statistics or tracking on memory allocations. 4 4 5 I don't usually associate the memory usage of the VirtualBox process with the guest because after booting the VM it's not empty with no services. It very quickly pulls several hundred megabytes of data from databases which are stored inefficiently in memory for high level scripting languages and processed constantly as fast as the network and CPU will allow. I find it very hard to believe that the memory usage of the VM host process corresponds to the memory usage of the guest in this case unless it is doing some impressive deduplication or similar . The guest starts with resident memory usage of over 2GB with another 1.5GB for cache and buffers.5 I don't usually associate the memory usage of the VirtualBox process with the guest because after booting the VM it's not empty with no services. It very quickly pulls several hundred megabytes of data from databases which are stored inefficiently in memory for high level scripting languages and processed constantly as fast as the network and CPU will allow. I find it very hard to believe that the memory usage of the VM host process corresponds to the memory usage of the guest in this case unless it is doing some impressive deduplication or similar (smaller page size, etc). The guest starts with resident memory usage of over 2GB with another 1.5GB for cache and buffers. 6 6 7 7 KiB Mem: 8198436 total, 6197632 used, 2000804 free, 692572 buffers
