| /external/rust/crates/grpcio-sys/grpc/tools/run_tests/performance/ |
| D | scenario_config_exporter.py | 25 # It can also be used to dump scenarios to files, to count scenarios by
79 for scenario in scenario_config.LANGUAGES[language].scenarios():
98 """Returns a function to filter scenarios to process."""
101 """Filters scenarios that match specified criteria."""
129 """Generates scenarios that match a given filter function."""
133 scenario_config.LANGUAGES[language_name].scenarios()))
136 def dump_to_json_files(scenarios: Iterable[Dict[str, Any]],
138 """Dumps a list of scenarios to JSON files"""
140 for scenario in scenarios:
144 # The dump file should have {"scenarios" : []} as the top level
[all …]
|
| D | README.md | 164 ### Generating scenarios
166 The benchmarks framework uses the same test scenarios as the legacy one. These
168 to export these scenarios to files, and also to count and analyze existing
169 scenarios.
171 The language(s) and category of the scenarios are of particular importance to
174 The following example counts scenarios in the `scalable` category:
197 189 total scenarios (category: scalable)
200 Client and server languages are only set for cross-language scenarios, where the
214 configurations for tests running a set of scenarios. The configurations are
220 of scenarios we intend to run (for instance, if we are generating configurations
[all …]
|
| /external/grpc-grpc/src/php/tests/qps/generated_code/Grpc/Testing/ |
| D | Scenarios.php | 12 * A set of scenarios to be run with qps_json_driver
14 * Generated from protobuf message <code>grpc.testing.Scenarios</code>
16 class Scenarios extends \Google\Protobuf\Internal\Message class
19 * Generated from protobuf field <code>repeated .grpc.testing.Scenario scenarios = 1;</code>
21 private $scenarios; variable in Grpc\\Testing\\Scenarios
29 * Generated from protobuf field <code>repeated .grpc.testing.Scenario scenarios = 1;</code>
34 return $this->scenarios;
38 * Generated from protobuf field <code>repeated .grpc.testing.Scenario scenarios = 1;</code>
45 $this->scenarios = $arr;
|
| /external/perfetto/protos/perfetto/config/chrome/ |
| D | scenario_config.proto | 58 // Chrome field tracing defines a set of scenarios, each associated with
59 // specific tracing configs, and nested scenarios that can cover interesting
60 // tracing regions within a parent scenario. Both scenarios and nested scenarios
67 // Start rules from all scenarios in the config are observed by default (when no
68 // scenario is active). Once enrolled in a specific scenario, other scenarios
69 // are ignored until the active one is exited. Start rules for nested scenarios
80 // scenario. All nested scenarios within the parent scenario will be observed
84 // tracing session, and attempts to upload the trace. All scenarios are
98 // discards the trace. All scenarios will be observed again.
101 // to upload the trace. All scenarios will be observed again.
[all …]
|
| /external/grpc-grpc/test/cpp/qps/ |
| D | json_run_localhost_scenarios.bzl | 1 """Scenarios run on localhost."""
3 …scenarios\' : [{"name": "cpp_protobuf_async_unary_75Kqps_600channel_60Krpcs_300Breq_50Bresp", "war…
|
| D | qps_json_driver_scenarios.bzl | 1 """Scenarios of qps driver."""
3 …scenarios\' : [{"name": "cpp_protobuf_sync_streaming_qps_unconstrained_insecure", "warmup_seconds"…
|
| D | qps_json_driver.cc | 204 // Parse into an array of scenarios in QpsDriver()
205 Scenarios scenarios; in QpsDriver() local
206 ParseJson(json.c_str(), "grpc.testing.Scenarios", &scenarios); in QpsDriver()
210 GPR_ASSERT(scenarios.scenarios_size() > 0); in QpsDriver()
212 for (int i = 0; i < scenarios.scenarios_size(); i++) { in QpsDriver()
214 const Scenario& scenario = scenarios.scenarios(i); in QpsDriver()
218 Scenario* scenario = scenarios.mutable_scenarios(i); in QpsDriver()
|
| /external/linux-kselftest/tools/testing/selftests/rcutorture/bin/ |
| D | config2csv.sh | 9 # By default, this script will take the list of scenarios from the CFLIST
10 # file in that directory, otherwise it will consider only the scenarios
13 # output file. Note that "CFLIST" is a synonym for all the scenarios in the
14 # CFLIST file, which allows easy comparison of those scenarios with selected
15 # scenarios such as BUSTED that are normally omitted from CFLIST files.
31 scenarios="`echo $scenariosarg | sed -e "s/\<CFLIST\>/$defaultconfigs/g"`"
40 for i in $scenarios
|
| /external/cronet/third_party/protobuf/benchmarks/protobuf.js/ |
| D | protobufjs_benchmark.js | 34 var scenarios = benchmarkSuite.newBenchmark(
36 scenarios.suite
54 protobufjs_decoding: scenarios.benches[0] * totalBytes,
55 protobufjs_encoding: scenarios.benches[1] * totalBytes
60 + scenarios.benches[0] * totalBytes / 1024 / 1024 + "MB/s" );
62 + scenarios.benches[1] * totalBytes / 1024 / 1024 + "MB/s" );
|
| /external/protobuf/benchmarks/protobuf.js/ |
| D | protobufjs_benchmark.js | 34 var scenarios = benchmarkSuite.newBenchmark(
36 scenarios.suite
54 protobufjs_decoding: scenarios.benches[0] * totalBytes,
55 protobufjs_encoding: scenarios.benches[1] * totalBytes
60 + scenarios.benches[0] * totalBytes / 1024 / 1024 + "MB/s" );
62 + scenarios.benches[1] * totalBytes / 1024 / 1024 + "MB/s" );
|
| /external/grpc-grpc/tools/run_tests/ |
| D | run_performance_tests.py | 122 'scenarios': [scenario_json]
347 """Create jobspecs for scenarios to run."""
351 scenarios = []
364 scenarios.append(
372 for scenario_json in language.scenarios():
425 scenarios.append(scenario)
427 return scenarios
505 help='Just list scenarios to be run, but don\'t run them.')
511 help='Regex to select scenarios to run.')
527 help='Run netperf benchmark as one of the scenarios.')
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/tools/run_tests/ |
| D | run_performance_tests.py | 127 json.dumps({'scenarios': [scenario_json]}))
355 """Create jobspecs for scenarios to run."""
359 scenarios = []
372 scenarios.append(
380 for scenario_json in language.scenarios():
433 scenarios.append(scenario)
435 return scenarios
515 help='Just list scenarios to be run, but don\'t run them.')
520 help='Regex to select scenarios to run.')
533 help='Run netperf benchmark as one of the scenarios.')
[all …]
|
| /external/mockftpserver/tags/2.0.2/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
31 FTP Scenarios Supported by FakeFtpServer
34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
83 scenarios not supported include:
105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.0/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
31 FTP Scenarios Supported by FakeFtpServer
34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
83 scenarios not supported include:
105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.0-rc1/MockFtpServer/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
31 FTP Scenarios Supported by FakeFtpServer
34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
83 scenarios not supported include:
105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.0.1/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
31 FTP Scenarios Supported by FakeFtpServer
34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
83 scenarios not supported include:
105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.0-rc3/MockFtpServer/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
31 FTP Scenarios Supported by FakeFtpServer
34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
83 scenarios not supported include:
105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.0-rc1/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
31 FTP Scenarios Supported by FakeFtpServer
34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
83 scenarios not supported include:
105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/cronet/third_party/protobuf/benchmarks/js/ |
| D | js_benchmark.js | 44 var scenarios = benchmarkSuite.newBenchmark(
46 scenarios.suite
64 protobufjs_decoding: scenarios.benches[0] * totalBytes / 1024 / 1024,
65 protobufjs_encoding: scenarios.benches[1] * totalBytes / 1024 / 1024
70 + scenarios.benches[0] * totalBytes / 1024 / 1024 + "MB/s" );
72 + scenarios.benches[1] * totalBytes / 1024 / 1024 + "MB/s" );
|
| /external/protobuf/benchmarks/js/ |
| D | js_benchmark.js | 44 var scenarios = benchmarkSuite.newBenchmark(
46 scenarios.suite
64 protobufjs_decoding: scenarios.benches[0] * totalBytes / 1024 / 1024,
65 protobufjs_encoding: scenarios.benches[1] * totalBytes / 1024 / 1024
70 + scenarios.benches[0] * totalBytes / 1024 / 1024 + "MB/s" );
72 + scenarios.benches[1] * totalBytes / 1024 / 1024 + "MB/s" );
|
| /external/mockftpserver/MockFtpServer/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
36 FTP Scenarios Supported by FakeFtpServer
39 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
65 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
89 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
90 scenarios not supported include:
112 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.3/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
36 FTP Scenarios Supported by FakeFtpServer
39 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
65 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
89 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
90 scenarios not supported include:
112 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.4/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
36 FTP Scenarios Supported by FakeFtpServer
39 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
65 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
89 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
90 scenarios not supported include:
112 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.5/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
36 FTP Scenarios Supported by FakeFtpServer
39 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
65 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
89 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
90 scenarios not supported include:
112 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
| /external/mockftpserver/tags/2.2/src/site/apt/ |
| D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios.
33 FTP Scenarios Supported by FakeFtpServer
36 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include:
62 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include:
86 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe…
87 scenarios not supported include:
109 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|