teleport/lib/config
Sasha Klizhentas 8356ae6a74 Use in-memory cache for the auth server API.
This commit expands the usage of the caching layer
for auth server API:

* Introduces in-memory cache that is used to serve all
Auth server API requests. This is done to achieve scalability
on 10K+ node clusters, where each node fetches certificate authorities,
roles, users and join tokens. It is not possible to scale
DynamoDB backend or other backends on 10K reads per seconds
on a single shard or partition. The solution is to introduce
an in-memory cache of the backend state that is always used
for reads.

* In-memory cache has been expanded to support all resources
required by the auth server.

* Experimental `tctl top` command has been introduced to display
common single node metrics.

Replace SQLite Memory Backend with BTree

SQLite in memory backend was suffering from
high tail latencies under load (up to 8 seconds
in 99.9%-ile on load configurations).

This commit replaces the SQLite memory caching
backend with in-memory BTree backend that
brought down tail latencies to 2 seconds (99.9%-ile)
and brought overall performance improvement.
2019-04-12 14:23:09 -07:00
..
configuration.go Kubernetes proxy to use impersonation API 2019-03-18 15:46:49 -07:00
configuration_test.go Use in-memory cache for the auth server API. 2019-04-12 14:23:09 -07:00
fileconf.go Use in-memory cache for the auth server API. 2019-04-12 14:23:09 -07:00
fileconf_test.go Don't read configuration section if it's not enabled. 2018-08-31 17:01:01 -07:00
testdata_test.go Don't read configuration section if it's not enabled. 2018-08-31 17:01:01 -07:00