題記
elasticsearch性能測試研究了很久,自己想過通過批量導入資料,然後記錄時間,統計CPU、記憶體等變化,計算得出某個性能名額。但顯然,資料量起伏不定,非常不準确。
研究發現,github上提供了rally作為elasticsearch的性能測試工具,較好的解決了es性能測試問題。
1、esrally功能:es的性能測試工具。
esrally不支援windows版本,目前隻支援Linux和Mac OS。
esrally的運作基于以下兩點假設:
1)所有運作在同一台機器完成。(未來改假設條件可能會去掉)
2)你需要向Elasticsearch索引中添加特定的資料集,然後在其上進行基準查詢(benchmarking queries).
2、esrally安裝:
前提:驗證是否安裝了以下内容(注意版本)
Python 3.4+ available as python3 on the path (verify with: python3 --version which should print Python 3.4.0 or higher)
pip3 available on the path (verify with pip3 --version)
JDK 8
git
如下所示:
[root@laoyang git-2.4.0]# python
Python 3.5.1 (default, Aug 2 2016, 09:53:20)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-17)] on linux
Type "help", "copyright", "credits" or "license" for more information.
[root@laoyang git-2.4.0]# git --version
git version 2.4.0
[root@laoyang git-2.4.0]# java -version
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
[root@laoyang git-2.4.0]# find / -name "pip3"
/usr/bin/pip3
/usr/local/python3/bin/pip3
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
步驟1:安裝 Rally
pip3 install esrally
步驟2:配置 Rally
調用: esrally configure 會提示讓你輸入 java8.home(也就是JAVA_HOME設定的環境變量路徑)。
僅java8.home使用自己本機的JAVA_HOME環境變量路徑,其他采用預設值即可。
[root@laoyang .rally]# cat /root/.rally/rally.ini
[meta]
config.version = 5
[system]
root.dir = /root/.rally/benchmarks
log.root.dir = logs
env.name = local
[source]
local.src.dir=/root/.rally/src #注意,此路徑并非elaticsearch安裝路徑。
remote.repo.url=https://github.com/elastic/elasticsearch.git
[provisioning]
local.install.dir = install
[runtime]
java8.home = /opt/jdk1.8.0_91 #注意,JAVA_HOME 路徑為:/opt/jdk1.8.0_91
[benchmarks]
local.dataset.cache = ${system:root.dir}/data
[reporting]
datastore.type = elaticsearch
datastore.host = 10.0.1.30
datastore.port = 9200
datastore.secure = False
datastore.user =
datastore.password =
[tracks]
default.url =
https://github.com/elastic/rally-tracks17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
步驟3:運作esrally
由于elasticsearch的運作必須非root賬戶。esrally建議用非root賬戶執行。
3、esrally執行常見問題及解決方案
問題1:版本用哪個版本?
目前用最新版本 Rally 0.3.2(2016-8-7發行)。
問題2:注意gradle需要2.13版本,高版本會不相容。
[root@laoyang caches]# ll /usr/bin/gradle
lrwxrwxrwx 1 root root 27 Aug 5 17:13 /usr/bin/gradle -> /opt/gradle-2.13/bin/gradle
問題3:安裝時候提示 documents.json.bz2 無法下載下傳成功。
1)手動下載下傳:
http://benchmarks.elasticsearch.org.s3.amazonaws.com/corpora/geonames/documents.json.bz22)移動到 /root/.rally/benchmarks/data/geonames/(對于root使用者)
對于非root使用者,elaticsearch使用者,移動路徑為:/home/elasticsearch/benchmarks/data/geonames/
問題4: esrally單獨運作和加參數運作差別?
esrally單獨運作:非常友善的指令,等價于 :esrally --pipeline=from-sources --version=current. Rally 将要通過Gradle從源碼編譯elasticsearch。
esrally --pipline=from-distribution --distribution-version=2.3.4, Rally将要從
https://download.elasticsearch.org/elasticsearch/release/org/elasticsearch/distribution/tar/elasticsearch/2.3.4/elasticsearch-2.3.4.tar.gz下載下傳elaticsearch2.3.4版本運作。
問題5: Could not resolve all dependencies for configuration ‘:benchmarks:classpath’.
37 > Could not download shadow.jar (com.github.jengelman.gradle.plugins:shadow:1.2.3)如何解決?
root賬戶下:
cd /home/elasticsearch/.rally/benchmarks/src
gradle :distribution:tar:assemble
正确提示資訊為:
deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:transport-netty4:processResources UP-TO-DATE
:modules:transport-netty4:classes
:modules:transport-netty4:jar
:modules:transport-netty4:copyPluginPropertiesTemplate
:modules:transport-netty4:pluginProperties
:modules:transport-netty4:bundlePlugin
:distribution:buildModules
:distribution:tar:buildTar
:distribution:tar:generatePomFileForNebulaPublication
:distribution:tar:signArchives SKIPPED
:distribution:tar:assemble
BUILD SUCCESSFUL
4、esrally最終運作結果:
Preparing for race (might take a few moments) ...
Building from sources ...
/home/elasticsearch/.rally/benchmarks/races/2016-08-08-07-29-59/local/logs/rally_out.logRacing on track [geonames] and challenge [append-no-conflicts] with car [defaults]
Benchmarking indexing at 12183.1 docs/s [100% done]
Benchmarking stats (warmup iteration 100/100) [100% done]
Benchmarking stats (iteration 100/100) [100% done]
Benchmarking search (warmup iteration 100/100) [100% done]
Benchmarking search (iteration 100/100) [100% done]
------------------------------------------------------
_______ __ _____
/ ____(_)___ ____ _/ / / ___/_________ ________
/ /_ / / __ \/ __ `/ / \__ \/ ___/ __ \/ ___/ _ \
/ __/ / / / / / /_/ / / ___/ / /__/ /_/ / / / __/
/_/ /_/_/ /_/\__,_/_/ /____/\___/\____/_/ \___/
| Metric | Value |
|----------------------------------------------------------:|----------:|
| Min Indexing Throughput [docs/s] | 11949 |
| Median Indexing Throughput [docs/s] | 12307 |
| Max Indexing Throughput [docs/s] | 13349 |
| Indexing time [min] | 164.045 |
| Merge time [min] | 32.3815 |
| Refresh time [min] | 8.82333 |
| Flush time [min] | 1.63852 |
| Merge throttle time [min] | 1.45482 |
| Query latency default (90.0 percentile) [ms] | 68.8676 |
| Query latency default (99.0 percentile) [ms] | 77.6009 |
| Query latency default (100 percentile) [ms] | 78.8328 |
| Query latency term (90.0 percentile) [ms] | 4.63227 |
| Query latency term (99.0 percentile) [ms] | 10.9506 |
| Query latency term (100 percentile) [ms] | 13.0573 |
| Query latency phrase (90.0 percentile) [ms] | 6.35018 |
| Query latency phrase (99.0 percentile) [ms] | 13.1745 |
| Query latency phrase (100 percentile) [ms] | 14.2399 |
| Query latency country_agg_uncached (90.0 percentile) [ms] | 361.913 |
| Query latency country_agg_uncached (99.0 percentile) [ms] | 384.75 |
| Query latency country_agg_uncached (100 percentile) [ms] | 392.645 |
| Query latency country_agg_cached (90.0 percentile) [ms] | 7.71451 |
| Query latency country_agg_cached (99.0 percentile) [ms] | 17.4704 |
| Query latency country_agg_cached (100 percentile) [ms] | 18.4851 |
| Query latency scroll (90.0 percentile) [ms] | 50.4234 |
| Query latency scroll (99.0 percentile) [ms] | 50.9866 |
| Query latency scroll (100 percentile) [ms] | 51.2115 |
| Query latency expression (90.0 percentile) [ms] | 482.02 |
| Query latency expression (99.0 percentile) [ms] | 485.951 |
| Query latency expression (100 percentile) [ms] | 491.999 |
| Query latency painless_static (90.0 percentile) [ms] | 890.382 |
| Query latency painless_static (99.0 percentile) [ms] | 918.354 |
| Query latency painless_static (100 percentile) [ms] | 927.282 |
| Query latency painless_dynamic (90.0 percentile) [ms] | 968.908 |
| Query latency painless_dynamic (99.0 percentile) [ms] | 1019.14 |
| Query latency painless_dynamic (100 percentile) [ms] | 1021.97 |
| Median CPU usage (index) [%] | 887.7 |
| Median CPU usage (stats) [%] | 94.9 |
| Median CPU usage (search) [%] | 445.05 |
| Total Young Gen GC [s] | 89.121 |
| Total Old Gen GC [s] | 12.274 |
| Index size [GB] | 3.30111 |
| Totally written [GB] | 20.2123 |
| Heap used for segments [MB] | 21.6794 |
| Heap used for doc values [MB] | 0.113129 |
| Heap used for terms [MB] | 20.0574 |
| Heap used for norms [MB] | 0.0761719 |
| Heap used for points [MB] | 0.770404 |
| Heap used for stored fields [MB] | 0.6623 |
| Segment count | 96 |
| Indices Stats(90.0 percentile) [ms] | 11.5116 |
| Indices Stats(99.0 percentile) [ms] | 14.1724 |
| Indices Stats(100 percentile) [ms] | 36.8348 |
| Nodes Stats(90.0 percentile) [ms] | 11.342 |
| Nodes Stats(99.0 percentile) [ms] | 13.435 |
| Nodes Stats(100 percentile) [ms] | 16.4768 |
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
Logs for this race are archived in /home/elasticsearch/.rally/benchmarks/races/2016-08-08-07-29-59/local/logs-geonames-append-no-conflicts-defaults.zip
5、問題大讨論
https://discuss.elastic.co/t/the-below-bugs-appers-when-running-esrally/57063/25源碼 作者danielmitterdorfer一一回複, 最終作者回複:
I am very happy too and I am glad you had so much persistence. You also uncovered a few usability problems that I need to tackle.
幫作者提了一些建議,促使他更新了一個版本0.3.2。
參考:
https://github.com/elastic/rally小結
前面的确費勁周折,花費了接近3整天實踐,期間甚至告訴原作者工具太難用,給作者反複溝通,最終問題解決。看到輸出結果的那一刻,整個人很興奮。堅持到底,相信付出的力量!不斷思考、反思中前行!