-
Notifications
You must be signed in to change notification settings - Fork 210
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
more efficient use of disk space on exports #3
Comments
Fixed tnx it was disk space.
|
Stu, I'm not sure how there could have been image placement work lost; perhaps you had been working on the map for 2.5 hours while the server was already down, but you hadn't refreshed your local browser window? Have you seen this happen again? If you do, could you create a new issue for it? I'm sorry you lost 2.5 hours of work, that sucks. I've been inundated with feature requests, bug reports, etc on Infragram and PublicLab.org, while also trying to get this big tag migration going and a new test server. I've blocked out some time right now to make MapKnitter more efficient on disk space usage, but it is so huge right now that we're going to have to move it onto a larger disk very soon. |
taking notes here; going through https://github.com/publiclab/mapknitter/blob/master/app/models/warpable.rb#L119 to find temp files from the export we can delete:
This should win us a lot of space.
|
Would it be worth trying to offload the temporary files to an S3 bucket? We could create a new bucket for a new task, name it based on the task, and We'll never run out of disk space, but you might get charged a few quarters On Thu, May 29, 2014 at 11:48 AM, Jeffrey Warren
|
The source files are already stored in s3 - actually the first operation is to copy them to a local folder so they can be manipulated. I think we can be very aggressive here without losing anything. like |
I'm going to start with deleting all -working directories and pngs, and leave the geo.tiff files, since they're used later in the export process. We can take this by stages. |
tested and running... doing bulk deletions now 148gb available after deleting pngs |
warren@tycho: So huge maps like http//mapknitter.org/map/view/mestia still have 2.7gb of geotiffs, but we've won a lot of space overall. |
after the working directories were deleted, we now have 162gb of space. And the exports should now clean up after themselves. |
If we need more later, we can delete all otherwise closing for now! |
No description provided.
The text was updated successfully, but these errors were encountered: