-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncompressed boxes for VMware and Parallels are to large #505
Comments
CC: @legal90 |
About Parallels Desktop - I guess that the situation will be much better with the next Packer version (0.9.0), due to |
@legal90 that improves Parallels boxes to be in parity with VMware, but it is still strange that VirtualBox is about 1/3 the size. Also the improvement isn't that significant on file systems other that ext3. For example btrfs and the BSD file systems. |
Now that 0.9.0 is out, how are we looking and is this still a concern? |
I think this is better since v0.9.0 but still VMware and Parallels boxes are x3 VirtualBox but that is probably something only VMware and Parallels them self can improve on. Closing for now. |
I have been digging a bit in the effectiveness of minimize.sh. My conclusion is that everything is good with VirtualBox.
E.g. CentOS 7.1 x86_64 produces a box that is 343 MB and uncompresses to 358 MB with minimisation, without it would be 485 MB and 505 MB.
But comparing that with VMware where a minimised box is 444 MB, but uncompresses to 1.1 GB! Without minimisation it is slightly worse with 606 MB and 1.5 GB.
It even gets worsewith Parallels where a minimised box is 407 MB and uncompressed1.6 GB1.0 GB.Why is VMware and Parallels x3 worse than VirtualBox on space efficiency? I think we need to find out and see if there is anything we can do about it.
All numbers I found out can be viewed in my spread sheet.
UPDATED: Updated numbers for Parallels after taking into account #505 (comment)
The text was updated successfully, but these errors were encountered: