Overpass API developpement

Text archives Help


Re: [overpass] compressed database info


Chronological Thread 
  • From: Donal Diamond <donal.diamond@gmail.com>
  • To: overpass@listes.openstreetmap.fr
  • Subject: Re: [overpass] compressed database info
  • Date: Fri, 27 Feb 2015 19:47:57 +0000

One more update - since I turned replication back on my map files have increased again since before my complete rebuild

9.6G    nodes.map
1.3G    ways.map

Previously I was using 0.7.4  with hourly updates and nodes.map was 8.0G

Has the new  --flush-size=0  argument something to do with this?

D



On 27 February 2015 at 19:38, Roland Olbricht <roland.olbricht@gmx.de> wrote:
Hi,

I applied the patches from minor_issues to my backend_compression branch
and built following
http://wiki.osm.org/wiki/Overpass_API/install#Installation

I imported by doing:
[...]
I'm seeing some space gain   from about 11GB -> 9 GB
[...]
Most of my space usage is from the nodes.map file which hasn't changed
- it is possible or feasible to compress the map files also?

Thank you for the tests and the documentation.

It revealed that the nodes.map is for smaller installations really the showstopper. The file has for all subsets of the OSM data roughly the same total size, and I decided that the 8 GB are of minor important from the perspective of the world database.

After reconsidering the issue, I think it is possible to add code to do the compression on the nodes.map file as well. The two possibilities are that I either do that myself, which may takt until at least end of March because I have scheduled FOSSGIS preparations and the server move right now.

Or somebody else will adopt the code from the .bin file storage. I'll do my best to help and then merge the result immeidately into the backend_compression branch.

Best regards,

Roland





Archive powered by MHonArc 2.6.18.

Top of page