| commit | 539a78419a0c9352c9ccc0a8ffa721c9f9a3a491 | [log] [tgz] |
|---|---|---|
| author | Jacob Barrett <jbarrett@pivotal.io> | Thu Nov 12 07:35:40 2020 -0800 |
| committer | GitHub <noreply@github.com> | Thu Nov 12 07:35:40 2020 -0800 |
| tree | c784b91a672bd37599a7d8590dcdd7fd275bdbb8 | |
| parent | 0d640d4073e733f6f0f45905373395d1acea52dc [diff] |
Adds peer to peer benchmarks. (#135) * Adds P2P put test benchmark. * Adds P2P get test benchmark. * Adds put bytes benchmark. * Adds SSL parameters to benchmarks. * Fixes API access for old releases.
This project contains a benchmarking framework and benchmarks for Apache Geode. It is based on the yardstick framework, but with a java based test configuration and test execution framework.
These benchmarks are under development.
The benchmarks require machines with passwordless ssh enabled in order to run, so ensure that the authentication key pair for SSH does not have a passphrase. If you have previously created a key pair with a passphrase, you can create a different key pair which is of a different type than the previously created one. Be sure to backup your existing key pair before creating a new one. The public key needs to be in PEM format, but some newer OpenSSH versions default to a new format. PEM format can be forced by using -m PEM:
ssh-keygen -m PEM -t rsa
While running a test on a single machine (i.e. localhost) add the generated key to authorized_keys to authorize the user:
cat <your_public_key_file> >> ~/.ssh/authorized_keys
Test if you can ssh to localhost:
ssh localhost
As long as that works, we are good to go.
Get your local hosts name:
hostname
Edit /etc/hosts and add the local host name with and without domain to localhost entries.
127.0.0.1 localhost mycomputer mycomputer.mydomain ::1 localhost mycomputer mycomputer.mydomain
To run all benchmarks, run the benchmark task and pass in a list of hosts.
For example:
./gradlew benchmark -Phosts=localhost,localhost,localhost,localhost
Options:
-Phosts : Hosts used by benchmarks on the order of client,locator,server,server (-Phosts=localhost,localhost,localhost,localhost)
-PoutputDir : Results output directory (-PoutputDir=/tmp/results)
-PtestJVM : Path to an alternative JVM for running the client, locator, and servers. If not specified JAVA_HOME will be used. Note all compilation tasks will still use JAVA_HOME.
-PwithSsl : Flag to run geode with SSL. A self-signed certificate will be generated at runtime.
-PwithSslProtocols : Specifies enabled SSL protocols. See Geode property `ssl-protocols`
-PwithSslCiphers : Specifies enabled SSL chipher suites. See Geode property `ssl-ciphers`
-PwithSecurityManager : Flag to start Geode with the example implementation of SecurityManager
-PwithGc : Select which GC to use. Valid values CMS (default), G1, Z.
-PwithHeap : Specify how large a heap the benchmark VMs should use, default "8g". Accepts any `-Xmx` value, like "32g".
-PwithThreads : Specify how many threads to use when executing the benchmark. Default varies by benchmark.
-PwithWarmup : Specify how long to warm up the benchmark in seconds. Default is 60 seconds.
-PwithDuration : Specify how long to measure the benchmark in seconds. Default is 300 seconds.
--tests : Specific benchmarks to run (--tests=PartitionedPutBenchmark)
-d : Debug
-i : Info
This project includes some scripts to automate running benchmarks in AWS and analyzing the results produced (as well as the results produced from running locally). See the README.md in the infrastructure/aws directory.
The project is divided into two modules
Benchmarks are defined in declarative configuration classes. Each configuration class is run as a junit test which calls the configure method and passes it to the TestRunner, which executes the test on the provided TEST_HOSTS.
Benchmarks are composed of before tasks, after tasks, and workload tasks. Each seperate before and after task is run once. Workload tasks are run repeatedly and their execution time is measured and reported by the yardstick framework.
/** * Benchmark configuration class, which defines the topology of the test and * the initialization tasks and workload tasks for the test. */ public class PartitionedPutBenchmark implements PerformanceTest { @Test public void run() throws Exception { TestRunners.defaultRunner().runTest(this::configure); } /** * Declare the configuration of the test by calling methods * on TestConfig. */ public TestConfig configure() { TestConfig testConfig = new TestConfig(); int locatorPort = 10334; //This test has three roles, a geode locator, server, and client config.role("locator", 1); config.role("server", 2); config.role("client", 1); //Define how the locator,server and client are initialized config.before(new StartLocator(locatorPort), "locator"); config.before(new StartServer(locatorPort), "server"); config.before(new StartClient(locatorPort), "client"); config.before(new CreatePartitionedRegion(), "server"); config.before(new CreateClientProxyRegion(), "client"); //Define the benchmarked workload, which runs in a client config.workload(new PutTask()); return config; } }
/** * Workload task, which extends the yardstick BenchmarkDriverAdapter * * Workload tasks should execute a single unit of work, and will be run repeatedly * for the duration of the test. */ public class PutTask extends BenchmarkDriverAdapter implements Serializable { private Region<Object, Object> region; @Override public void setUp(BenchmarkConfiguration cfg) throws Exception { super.setUp(cfg); ClientCache cache = ClientCacheFactory.getAnyInstance(); region = cache.getRegion("region"); } @Override public boolean test(Map<Object, Object> ctx) throws Exception { region.put(1,2); return true; } }
On AWS, you can run any benchmark on a topology that routes all client-server communication through an SNI proxy (HAproxy).
To run a test, e.g. PartitionedGetBenchmark, with SNI:
./run_tests.sh -t anytagname -- -PwithSniProxy '--tests=PartitionedGetBenchmark'
Since SNI is a feature of TLS, running with the SNI topology incurs TLS overheads.
StartSniProxy runs on proxy node-PwithSSL/-DwithSSL=true when running SNI testshaproxy.cfg with client-visible SNI hostnamessetPoolSocketFactory in a new StartClientSNI task--hostname-for-clients on locator and servers for SNIPrePopulateRegion.run() and in PartitionedPutBenchmark[SNI] yakeyRange back to 1e6 in PartitionedPutBenchmark[SNI] after client-server connections are healthy-PwithSniProxy/-DwithSniProxy=true flagharness module dependency on Geode by moving Geode keystore/truststore setting out of harness module and up into geode-benchmarks i.e. set 'em in properties sent to Locator.startLocatorAndDS in StartLocator, StartServerdocker-compose.yml distribution out of harness module up into geode-benchmarks so it gets distributed whenever it changes (without requiring rebuilding AWS AMI and cluster on AWS)StartServer task use ServerLauncher (instead of CacheFactory) for symmetry with LocatorLauncher—also too: encapsulation!./run_tests.sh sometimes seems to hang after benchmarks have completed, requiring operator to enter ^C to un-stick itrsync: Git “scheme” work in run_tests.sh script for benchmark repo (not just for geode repo)