1be2f4b8e2
Documentation: Restructure directory to accommodate new site generation system
...
Signed-off-by: lucperkins <lucperkins@gmail.com>
2020-01-21 14:29:54 -08:00
a621d807f0
documentation: initial metadata additions for website generation ( #10596 )
...
Signed-off-by: lucperkins <lucperkins@gmail.com>
2019-04-01 13:57:24 -07:00
ca47aab373
*: fix typos in markdown docs
2018-03-07 10:32:07 -05:00
31c1931b7b
Docs: replace absolute links with relative ones.
2017-04-04 15:21:42 -07:00
e0de6536c8
etcd-2-1-0-bench: Fix an absolute bare link to resource outside of Documentation dir
2017-03-22 15:27:21 -07:00
c8a2c7f64f
*: eschew you from documentation
...
Removed line wrapping in affected files as well.
2017-03-06 11:40:46 -08:00
4eefdaa4bb
hack/benchmark: change boom to hey
...
boom has moved to hey, due to a conflicting binary name with another
project
2016-10-24 13:28:53 -07:00
61cfe68247
Documentation: v3 mem benchmark total watch value
...
Updating Documentation/benchmarks/etcd-3-watch-memory-benchmark.md with the correct 'total watching' value
2016-04-13 14:12:10 -04:00
4e6289b829
doc: add benchmark result for 2.2
2016-03-07 12:00:42 -08:00
2510cacd47
docs: Relink and fix broken links
2016-02-25 12:42:11 +01:00
6f3ce70b46
docs/benchmarks: small fix in memory benchmark
2015-11-18 19:20:18 -08:00
37d3d20211
doc: add etcd3 watch benchmark doc
...
The primary goal of this doc is to confirm the memory
consumption of watch is as expected. Each connection
consumes O(10kb) of memory. Each stream consumes O(10kb)
of memory. Each watching consumes < O(1kb) of memory.
Then when you have a large number of watching with small
number of connections and streams, the ave memory consumption
per watch will be O(1kb).
2015-11-15 16:38:09 -08:00
a27a6b1372
Doc: fix typos for v3benchmark
...
The official benchmakr code seems to be in `tools` directory (not in `hack`).
2015-11-08 19:38:49 -08:00
e3cedeeb12
doc: add benchmark doc for new storage pkg
2015-10-22 13:53:03 -04:00
91b5b247e9
docs/benchmark: add 2.2.0-rc memory usage benchmark
...
It records the memory usage for different average value size, and
records the data size limitation.
2015-09-04 18:27:49 -07:00
753a079700
docs/benchmark: add benchmark result links in README
2015-08-27 17:08:49 -07:00
425afa66ea
docs/benchmarks: update bench version for more accuracy
2015-08-27 17:08:30 -07:00
605f0ce730
docs/benchmark: update etcd 2.2 bench
...
This benchmark is for etcd 2.2 rc after fixing several performance
downgrade bugs.
2015-08-27 16:52:55 -07:00
3632a1b9b1
*: add initial read benchmark for etcd v3
...
It includes the initial read benchmark for etcd v3.
This is the first step to give some rough thoughts. I haven't digged
deeper to answer some questions, including why its performance is not
better than HTTP + json, why one put will cause performance downgrade.
2015-08-25 07:50:18 -07:00
807de81172
docs/benchmarks: add benchmark result for 2.2
...
And it analyzes the reason for performance changes.
2015-08-19 23:59:33 -07:00
0949cc06e6
docs/benchmarks: doc benchmark tool
2015-06-24 15:11:08 -07:00
4a38788b2f
Documentation: add initial benchmarks
2015-03-06 09:32:24 -08:00
lucperkins