Created attachment 25587 [details] [review] Adds a HARDWARE REQUIREMENTS section to the INSTALL.ubuntu file When I installed Koha for the first time on Ubuntu, I provisioned a VM with what I assumed would be a generous 4GB of disk space. This turned out to be a very bad assumption due to the 2.3GB that a full git clone of the Koha repository requires. The symptoms of running out of disk space were sadly not immediately apparent and caused much head scratching. Therefore, in INSTALL.ubuntu, include an upfront note about hardware requirements in the case of a git install, in the hopes that others will not end up experiencing a similar fate :)
I agree with the idea. However, you forgot to account for data size. The sizes you suggest are far too small to actually import and fully reindex a small production system set of data. Please change to 20GB, and I'll sign off. ;)
Last I checked a full clone of git was just over 1GB. A bare install of Ubuntu is let's say 2GB. I am using a 15GB VM, and I only have 2.7GB left. My data is about 45K records. Also, it doesn't matter if it is a VM or not VM.
Created attachment 25622 [details] [review] Bug 11830 - Missing Disk Space recommendation for installation This adds a section which recommends at least 20GB disk space to the INSTALL.ubuntu file.
I've put up a revision. Feel free to sign it off, Dan.
M. Tompsett - I didn't forget to account for data size. As far as I know nobody recommends running Koha from git for production purposes; my assumption is that someone running from git is using it for development purposes. In which case most developers are going to be using a small data set, or will provision according to the size of their data. What I'm trying to establish is a reasonable minimal baseline. After "git clean -f" and "git reset --hard HEAD", "du -hs kohaclone" shows me a disk space usage of 1.9 GB. After running "perl Makefile.PL" and "make", "du -hs kohaclone" shows me a disk space usage of 2.3 GB. After running "make install", "du -hs /home/koha/koha-dev" then shows me disk space usage of 401 MB. Thus, a minimal git install requires 2.7 GB of free space... rounding up to the 3 GB I recommended in my original patch seems reasonable. On my 6.0 GB Ubuntu VM, here's what "df -h" shows after a minimal install and a load of approximately 1000 MARC records: Filesystem Size Used Avail Use% Mounted on /dev/mapper/koha--vg-root 5.6G 4.9G 413M 93% / udev 992M 4.0K 992M 1% /dev tmpfs 401M 276K 401M 1% /run none 5.0M 0 5.0M 0% /run/lock none 1002M 0 1002M 0% /run/shm /dev/vda1 228M 78M 138M 37% /boot I stand by my original patch as-is, as it uses the terms "at least" to target the minimal case for a git install and for the minimal VM size.
Some people may actually want to load real data for testing. Larger is better.
(In reply to M. Tompsett from comment #6) > Some people may actually want to load real data for testing. Larger is > better. Yes, but those people are going to know how large their data is and can determine how much disk space they will need on top of the documented minimum requirements. If you want to provide a metric like "If you have 1 GB of MARC binary records, you should provision 3 GB of space to allow for indexing, etc", then I think that would be a helpful addition.
To reflect the state of affairs correctly, I'm setting this to in-discussion and un-obsoleting Dan's patch. Mark: please do not automatically obsolete the original patch when you're counter-patching. As I've expressed on koha-devel, I believe that a better place for system specs, including for devs, is on the wiki or main website. As far as the two patches are concerned, Dan's numbers add up. I agree that a metric for estimating disk space per 1K bib records would be useful.
(In reply to Dan Scott from comment #7) > If you want to provide a metric like "If you have 1 GB of MARC binary > records, you should provision 3 GB of space to allow for indexing, etc", > then I think that would be a helpful addition. One number that's reasonably conservative for small to medium-sized databases: 55M of disk per 1,000 MARC21 bib records for Zebra and MySQL storage.
Final comment for now -- whatever form the specs take, there should be a clear distinction between specs for devs and specs for production, with some padding for production. This is because while a lot of small Koha database could in fact reasonably live on a system with only 10G of disk -- I've seen far too many Koha setups where insufficient attention is paid to monitoring disk usage to want the official community recommendation to be too low. In other words, I'm fine with Dan's suggestion of minimum 6G for development setups, but prefer Mark's suggestion of 20G for production usage.
(In reply to Galen Charlton from comment #10) > As I've expressed on koha-devel, I believe that a better place for system > specs, including for devs, is on the wiki or main website. That sounds good to me, as long as there's a clear pointer from the INSTALL.* files to the appropriate URL for hardware requirements.
Okay. How about here: http://koha-community.org/download-koha/ We could add some statement to the point list like: * Hard drive space recommendations include >=6 GB for a minimal development install, >= 20GB for a production install And then add that link to the USEFUL REFERENCE LINKS section like: Download (requirements, etc.): http://koha-community.org/download-koha/ Perhaps even include a link to a wiki page which flushes out disk space and memory suggestions?
Bug 17626 removed the INSTALL.* files, so this bug is no longer relevant.