-
Notifications
You must be signed in to change notification settings - Fork 30
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
Document required disk space #13
Comments
So far I can only report a lower bound of currently 740GB disk space used by postgres with the only DB being the indexer. Postgres itself reports a DB size of 692GB (either overhead or Gibi/Giga difference). I'll have to get a bigger SSD before continuing the test as my system partition is running full and I figured putting the DB on RAID6 with spinning disks won't do me any good either 😂 This will also give me the opportunity to compare the performance as my current setup (SATA SSD in software RAID1 encrypted and with LVM on top) seems rather slow, maxing out at 15k tx/s and taking days to build the indices. The bottleneck is definitely the DB/io. |
@sgeisler thanks a lot for the report! Looks like I will have to get a big SSD before I play with it. |
First of all, this project looks really cool! I hope I will be able to play with it at some point. :) Maybe even package it into my deb repo at some point.
I'd like to know the system requirements, especially disk space and I think it'd be useful to have it in the README.
The text was updated successfully, but these errors were encountered: