Re:Tile38 – Realtime geofencing and geospatial index, v1.7.0
by Fiahil on Friday December 30, 2016 @04:04PM
(#13287426)
Neat! Does someone already used it in production? I'm wondering if it could be useful to replace a medium sized postgres database. I'm trying to replace some clustering currently done with Elasticsearch with postgis, but it's really slow (6m points * 700 boxes, it's taking 20 minutes to scan the table).
[ Parent
| on HN ]
Re:Tile38 – Realtime geofencing and geospatial index, v1.7.0
by tidwall on Friday December 30, 2016 @04:31PM
(#13287641)
Yes, it is being used in production.
General purpose spatial queries with Tile38 are very fast. Likely much quicker than PostGIS, but PostGIS will be able to store much more data. It's a tradeoff for sure.
If your dataset isn't terribly big and performance is what you're after then I recommend giving Tile38 a try.
Re:Tile38 – Realtime geofencing and geospatial index, v1.7.0
by Fiahil on Friday December 30, 2016 @06:48PM
(#13288502)
Thank you for the details! After all, if I can manage to fit around 6 million points into a single r4.large and get a decent response time when clustering them, I can't see why I shouldn't try something with it as a secondary data store.