mirror
/
tile38
mirror of https://github.com/tidwall/tile38.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
968 Commits 14 Branches 101 Tags 54 MiB
Commit Graph

64 Commits

Author SHA1 Message Date
tidwall 6bdc77d59d Update btree 2021-04-26 10:50:09 -07:00
tidwall 5a1275bac2 Update BuntDB 2021-04-01 12:30:59 -07:00
tidwall 87a3ed5f0a Fix invalid queue.db error 2021-03-30 15:38:42 -07:00
tidwall bac9cebc51 Upgrade go.mod 2021-03-30 08:09:03 -07:00
tidwall 31a0fbd228 Upgrade gjson 2021-03-30 07:17:01 -07:00
tidwall 72dfaaec63 Updated dependencies 2021-02-07 17:54:56 -07:00
tidwall 4f8bc0531e Updated rtree library 2021-02-04 09:50:13 -07:00
tidwall b37e7395a3 Updated rtree library 2021-02-04 08:21:08 -07:00
tidwall 3ed048242e Various updates 
- Updated all dependencies
- Updated geoindex Box api
 2021-02-03 14:30:55 -07:00
tidwall 263bbd9dcc Updated packages 2021-01-25 15:11:55 -07:00
tidwall 016f397124 Replace tinybtree 2021-01-25 14:34:40 -07:00
tidwall 79bee8523b Updated btree deps 2020-10-27 15:29:50 -07:00
tidwall b1dc463c41 Updated dependencies 2020-09-22 16:43:58 -07:00
tidwall b3dc025545 Optimize point in ring 2020-03-25 15:07:14 -07:00
tidwall 957233c298 Fixed issue with some features not working with WITHIN 
This bug was fixed in the geojson dependency.

https://github.com/tidwall/geojson/pull/15

Closed #539
 2020-03-21 17:38:14 -07:00
tidwall c567512600 Fix packages not vendoring on build 2020-02-11 11:02:15 -07:00
tidwall 6f3716a0cf Fixes a false negative for intersecting rings 
https://github.com/tidwall/geojson/commit/ac08098
 2019-11-28 10:13:00 -07:00
tidwall cfc65a13f6 Refactor repository and build scripts 
This commit includes updates that affects the build, testing, and
deployment of Tile38.

- The root level build.sh has been broken up into multiple scripts
  and placed in the "scripts" directory.

- The vendor directory has been updated to follow the Go modules
  rules, thus `make` should work on isolated environments. Also
  some vendored packages may have been updated to a later
  version, if needed.

- The Makefile has been updated to allow for making single
  binaries such as `make tile38-server`. There is some scaffolding
  during the build process, so from now on all binaries should be
  made using make. For example, to run a development version of
  the tile38-cli binary, do this:
     make tile38-cli && ./tile38-cli
  not this:
     go run cmd/tile38-cli/main.go

- Travis.CI docker push script has been updated to address a
  change to Docker's JSON repo meta output, which in turn fixes
  a bug where new Tile38 versions were not being properly pushed
  to Docker
 2019-11-18 10:33:15 -07:00
tidwall 4b17a1b828 Nuke vendor directory 2019-11-17 15:01:07 -07:00
tidwall b27f32a66e Updated to Go modules 2019-11-17 14:38:27 -07:00
tidwall 23b016d192 Fix excessive memory usage for objects with TTLs 
This commit fixes an issue where Tile38 was using lots of extra
memory to track objects that are marked to expire. This was
creating problems with applications that set big TTLs.

How it worked before:

Every collection had a unique hashmap that stores expiration
timestamps for every object in that collection. Along with
the hashmaps, there's also one big server-wide list that gets
appended every time a new SET+EX is performed.

From a background routine, this list is looped over at least
10 times per second and is randomly searched for potential
candidates that might need expiring. The routine then removes
those entries from the list and tests if the objects matching
the entries have actually expired. If so, these objects are
deleted them from the database. When at least 25% of
the 20 candidates are deleted the loop is immediately
continued, otherwise the loop backs off with a 100ms pause.

Why this was a problem.

The list grows one entry for every SET+EX. When TTLs are long,
like 24-hours or more, it would take at least that much time
before the entry is removed. So for databased that have objects
that use TTLs and are updated often this could lead to a very
large list.

How it was fixed.

The list was removed and the hashmap is now search randomly. This
required a new hashmap implementation, as the built-in Go map
does not provide an operation for randomly geting entries. The
chosen implementation is a robinhood-hash because it provides
open-addressing, which makes for simple random bucket selections.

Issue #502
 2019-10-29 11:19:33 -07:00
tidwall 5abadd72a3 Updated geoindex 2019-09-19 11:30:49 -07:00
tidwall 639f6e2deb Replaced boxtree for rbang 2019-09-12 18:42:53 -07:00
tidwall 54f14d8b03 Updated gjson library 2019-08-15 06:08:38 -07:00
tidwall 85b70e0d26 Updated geojson package 2019-06-28 10:01:12 -07:00
tidwall 3ae59274e3 Removed evio option 2019-04-26 11:50:49 -07:00
tidwall 5ae1a76450 Updated dependencies 2019-03-14 09:55:31 -07:00
tidwall 4e656ad19b Fixed nearby inaccuracy with geofence 
Closes #431
 2019-03-12 14:38:05 -07:00
tidwall 30f903bd51 Require properties member for geojson features 2019-02-12 06:49:13 -07:00
tidwall 92c1ce8ef9 Update tinybtree dep 2019-02-11 13:39:29 -07:00
Steven Wolfe 1e775bf59b Adding ARM and ARM64 packages 2019-01-14 12:38:11 -07:00
Steve Lacy 74809188f6
Update geojson dependency 2019-01-10 09:37:20 -07:00
tidwall c75a144b83 Fixed MultiPolygon intersect failure 
close #394
 2018-12-03 17:19:18 -07:00
tidwall 1bdc2135d7 Update geojson vendor 2018-11-11 09:33:58 -07:00
tidwall a160fa0860 wip: cricle 2018-11-11 09:05:26 -07:00
tidwall 44edf52f97 Updated benchmark tool 2018-11-11 09:05:11 -07:00
tidwall 372744b192 More hacking vendored circle.go 2018-11-11 09:04:00 -07:00
tidwall edf5d22095 Hack geojson circle.go 2018-11-11 09:03:47 -07:00
tidwall 0cd6d164d6 Update evio 2018-11-05 12:07:18 -07:00
Alex Roitman 949371fcd9 Update geojson 2018-11-01 13:49:39 -07:00
tidwall 555e47036c Replaced net package with evio 
- Added threads startup flag
- Replaced net package with evio
- Refactored controller into server
 2018-10-28 15:51:47 -07:00
tidwall 745579b56b Updated geojson packages 2018-10-27 09:23:29 -07:00
Alex Roitman 33530075a4 Use new Meters() function. 2018-10-25 17:00:19 -07:00
tidwall b1370332e6 Always use compressed indexing 2018-10-23 11:23:55 -07:00
tidwall a9a1612972 Update geojson package 2018-10-22 05:40:56 -07:00
tidwall 7cc4008442 Added multiple indexing kinds 2018-10-21 19:08:56 -07:00
tidwall 3e41a2ecce Update gjson/sjson 2018-10-18 06:30:41 -07:00
tidwall cc75cf22a8 Fix #369 poly in hole query 2018-10-18 06:28:31 -07:00
tidwall 1544f2914d Fix Circle type 2018-10-16 08:55:26 -07:00
tidwall 6257ddba78 Faster point in polygon / GeoJSON updates 
The big change is that the GeoJSON package has been completely
rewritten to fix a few of geometry calculation bugs, increase
performance, and to better follow the GeoJSON spec RFC 7946.

GeoJSON updates

- A LineString now requires at least two points.
- All json members, even foreign, now persist with the object.
- The bbox member persists too but is no longer used for geometry
  calculations. This is change in behavior. Previously Tile38 would
  treat the bbox as the object's physical rectangle.
- Corrections to geometry intersects and within calculations.

Faster spatial queries

- The performance of Point-in-polygon and object intersect operations
  are greatly improved for complex polygons and line strings. It went
  from O(n) to roughly O(log n).
- The same for all collection types with many children, including
  FeatureCollection, GeometryCollection, MultiPoint, MultiLineString,
  and MultiPolygon.

Codebase changes

- The pkg directory has been renamed to internal
- The GeoJSON internal package has been moved to a seperate repo at
  https://github.com/tidwall/geojson. It's now vendored.

Please look out for higher memory usage for datasets using complex
shapes. A complex shape is one that has 64 or more points. For these
shapes it's expected that there will be increase of least 54 bytes per
point.
 2018-10-13 04:30:48 -07:00