cosbench #403
Open
cosbench #403
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…node" This reverts commit 7a11767.
intel-cloud#210 multiple drivers on the same physical node
This reverts commit fcd3f30.
This reverts commit ccd1dbf.
Dumping of Per driver results intel-cloud#221
patch for multi driver
version unify for issue intel-cloud#101
Signed-off-by: ywang19 <yaguang.wang@intel.com>
Signed-off-by: ywang19 <yaguang.wang@intel.com>
0.4.2.0 #5 real-time performance graph
… system time (cherry picked from commit d4e7088)
Each workload generate statistics to be exported to prometheus Fetch URI is /prometheus, URL is http://IP:port/controller/prometheus By default active and historical workloads are exported, archive workloads are not. To change the behaviour add the following defines to the start parameters of the controller or driver (in cosbench-start.sh L46): * -Dprometheus.export.workloads.active=false * -Dprometheus.export.workloads.historical=false * -Dprometheus.export.workloads.archive=true
As it's used widely in path creation, it causes exceptions and fails to archive workloads result.
- add prometheus.export.timeout to control if and how long to wait before stopping to export finished metrics - fix prometheus.export.workloads parameters name
(default to log/mission)
V0.4.5: Add Prometheus export for cosbench
- New system property: cosbench.controlleruse_only_active_drivers - if set to true, when launching a workload, only active drivers (the one that respond OK to pings) are used - default to false: All drivers are used and if one is not running the workload can't start with ConnectionError Exception
plus clean WS and add license
* global whitespace and line return cleaning * Add missing license headers
Recent JVMs run with OmitStackTraceInFastThrow enabled by default. When an exception occurs several times, the stack trace is no more generated, but COSBench still tries to parse it, and fails miserably. One solution is to run COSBench with -XX:-OmitStackTraceInFastThrow. For extra security we will also ignore such empty stack traces. Fixes: intel-cloud#323 Fixes: intel-cloud#331
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cosbench