To evaluate how much memory tile38 will use about tile38 HOT 4 CLOSED

I get it，thank you :)

from tile38.

Before loading the AOF file in tile38, is there a relatively conservative and simple method to evaluate how much memory tile38 will use ?

Every object comprises of at least:

• Object Header: 16-bytes
• R-Tree Pointer: 16-bytes

Then there's the actual data such as:

• Point Object (Lat/Lon): 16-bytes
• LineString: (Point*N)
• Polygon: (LineString*N)
• Etc..

So the smallest object is a Point which will take at least 48 bytes to store.

In addition, in order to reduce memory fragmentation, do you have any suggestion on the design of GeoJSON ?

Tile38 stores GeoJSON in a binary format, and any variation of the same fields are stored identically. For example:

{
  "type": "Point",
  "coordinates": [10,10]
}

and

{"coordinates": [10,10],"type":"Point"}

are the same as far as Tile38 is concerned. Both formats use the same amount of data.

I hope this information helps, and let me know if you have any additional questions.

from tile38.

I would also like to add that you can always check the memory usage with the SERVER command.

from tile38.

One more thing. If you are on a low-memory system, you can compile for 32-bits and save some memory.

From the command line:

$ GOARCH=386 make

The pointer sizes will be 32bits and this will save about 8 bytes per object.

from tile38.