From d0ad8b397108f3768cb3a311c9bd2ff230721f9c Mon Sep 17 00:00:00 2001 From: Tomasz Setkowski Date: Thu, 2 Nov 2017 14:03:19 +0000 Subject: [PATCH] release 0.2.0 --- CHANGELOG.md | 10 ++++++---- README.md | 2 +- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5785e93..b7d3454 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,8 +1,10 @@ -### 0.2.0 - Unreleased +### 0.2.0 (2017-Nov-02) -Add caching proxy with v3 API, including - - DBreeze backend - - Periodic cache invalidation based on upstream changes + * Add caching proxy with v3 API, including + - DBreeze backend + - Periodic cache invalidation based on upstream changes + * Adds stress tests + * Tweaked kestrel options to get better performance ### 0.1.2 (2017-Oct-31) diff --git a/README.md b/README.md index 4f5b9b9..ef3d096 100644 --- a/README.md +++ b/README.md @@ -176,7 +176,7 @@ The stress tests run 3. Then 6 workers run `paket install -f` via liget caching proxy V3 API. Under these conditions: - * cache download performance is *good*. The 6 workers end download within 7 minutes and are mostly constrained by IO limit. Same test on my local machine on SSD drive, passes in 3 minutes. + * cache download performance is *good*. The 6 workers end download within 9 minutes and are mostly constrained by IO limit. Same test on my local machine on SSD drive, passes in 3 minutes. * memory usage reported by docker stats peaks at about 520 MB. So docker mem_limit of 550MB-600MB makes sense. # Development