- 14 7月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* Performance: remove the synchronous persistence mechanism from batch ElasticSearch DAO. Because the current enhanced persistent session mechanism, don't require the data queryable immediately after the insert and update anymore. * Performance: share `flushInterval` setting for both metrics and record data, due to `synchronous persistence mechanism` removed. Record flush interval used to be hardcoded as 10s. * Remove `syncBulkActions` in ElasticSearch storage option. * Increase the default bulkActions(env, SW_STORAGE_ES_BULK_ACTIONS) to 5000(from 1000). * Increase the flush interval of ElasticSearch indices to 15s(from 10s) Add these 2 references. According to these, **(same _index, _type and _id) in same bulk will be in order** 1. https://github.com/elastic/elasticsearch/issues/50199 2. https://discuss.elastic.co/t/order-of--bulk-request-operations/98124 Notice, the order of different bulks is not guaranteed by the ElasticSearch cluster. We are going to have the risk of dirty write. But consider we set over 20s period between flush, and index flush period is 10, we should be safe. Recommend 5000 bulk size and 15s flush interval only. The persistent period has been set to 25s.
-
- 13 7月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
-
- 09 7月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
Groovy naturally supports many dynamic features that we don't benefit for now but cost performance loss, in this patch we compile our Groovy-based DSL scripts statically to optimize performance.
-
- 08 7月, 2021 1 次提交
-
-
由 whl12345 提交于
-
- 07 7月, 2021 1 次提交
-
-
由 Switch 提交于
-
- 06 7月, 2021 1 次提交
-
-
由 Sergi Castro 提交于
* Allow configuring max request header size This allows configuring the HTTP max request header size from the jetty server. By default it uses 8192, the same jetty default.
-
- 05 7月, 2021 1 次提交
-
-
由 Daming 提交于
-
- 03 7月, 2021 1 次提交
-
-
由 liqiangz 提交于
-
- 01 7月, 2021 2 次提交
- 30 6月, 2021 1 次提交
-
-
由 wu-sheng 提交于
1.0Performance: Add L1 aggregation flush period, which reduces the CPU load and helps young GC. 2. Replace do not direct send after the first aggregation to reduce the network #6400. 3. Enhance the DataCarrier to notify the consumer in no enqueue event in short term. 4. L1 aggregation flush period still works even no further metrics generated, powered by <3> 5. Fix gRPC remote client OOM. The concurrency control mechanism failed.
-
- 29 6月, 2021 1 次提交
-
-
由 Alvin 提交于
-
- 28 6月, 2021 1 次提交
-
-
由 liqiangz 提交于
-
- 22 6月, 2021 2 次提交
-
-
由 Tomasz Pytel 提交于
-
由 wallezhang 提交于
-
- 20 6月, 2021 1 次提交
-
-
由 wankai123 提交于
-
- 19 6月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
* OAL supports generating metrics from events * Add new dashboard for event metrics * Add some docs for event metrics
-
- 17 6月, 2021 1 次提交
-
-
由 Tomasz Pytel 提交于
-
- 11 6月, 2021 2 次提交
- 28 5月, 2021 2 次提交
- 27 5月, 2021 2 次提交
- 20 5月, 2021 1 次提交
-
-
由 hailin0 提交于
-
- 16 5月, 2021 1 次提交
-
-
由 Tomasz Pytel 提交于
-
- 13 5月, 2021 1 次提交
-
-
由 Zhenxu Ke 提交于
-
- 07 5月, 2021 2 次提交
- 27 4月, 2021 1 次提交
-
-
由 Ax1an 提交于
-
- 26 4月, 2021 1 次提交
-
-
由 高云峰 提交于
-
- 25 4月, 2021 1 次提交
-
-
由 liqiangz 提交于
-
- 23 4月, 2021 1 次提交
-
-
由 Darcy 提交于
-
- 19 4月, 2021 2 次提交
- 17 4月, 2021 1 次提交
-
-
由 guyang 提交于
-
- 15 4月, 2021 1 次提交
-
-
由 Daming 提交于
-
- 14 4月, 2021 1 次提交
-
-
由 Daming 提交于
-
- 13 4月, 2021 1 次提交
-
-
由 wankai123 提交于
-
- 08 4月, 2021 1 次提交
-
-
由 wankai123 提交于
-