[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3319: ---------------------------------- Similar issue occurs when comparing size of pack in the installer to actual on-disk footprint. I used jboss-devstudio-8.0.1.CR1-v20141207-0100-B352-installer-standalone.jar (a *549M file*) and got these numbers: {quote} Required Disk Space (as reported by installer): *426.22 MB* Actual disk space used by install, `du -shc`: *660M* After first startup, `du -shc`: *676M* {quote} Suspect the problem is that the pack size IN the installer jar is smaller than its unpacked size on disk. Because zips/jars are smaller than folders. So how do we better estimate the installed footprint size, given that the pack in the installer contains jarred plugins/features, which will be further unpacked during the install? And there's also more stuff that's unpacked/downloaded on the first startup (16M of stuff, according to my test above). Should we just do a few installs/startups (on various OSes and filesystems [NTFS, FAT32, ext4, whatever OSX uses] and round that number up, then just *hard code* that into the installer, instead of trying to calculate size [1]? [1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/... [~dgolovin] [~ldimaggio] WDYT? -- This message was sent by Atlassian JIRA (v6.3.11#6341)