You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
# CloudSuite 3.0 #
2
2
3
+
**This branch is an archive where all CloudSuite 3.0 benchmarks are stored. All prebuilt images are available at [cloudsuite3][old] at dockerhub. If you're searching for CloudSuite 4.0, please checkout [master][master] branch.**
4
+
3
5
[CloudSuite][csp] is a benchmark suite for cloud services. The third release consists of eight applications that have
4
6
been selected based on their popularity in today's datacenters. The benchmarks are based on real-world software
5
7
stacks and represent real-world setups.
@@ -26,3 +28,5 @@ We encourage CloudSuite users to use GitHub issues for requests for enhancements
Copy file name to clipboardExpand all lines: docs/benchmarks/data-caching.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,32 +31,32 @@ We will attach the launched containers to this newly created docker network.
31
31
### Starting the Server ####
32
32
To start the server you have to first `pull` the server image and then run it. To `pull` the server image use the following command:
33
33
34
-
$ docker pull cloudsuite/data-caching:server
34
+
$ docker pull cloudsuite3/data-caching:server
35
35
36
36
It takes some time to download the image, but this is only required the first time.
37
37
The following command will start the server with four threads and 4096MB of dedicated memory, with a minimal object size of 550 bytes listening on port 11211 as default:
We assigned a name to this server to facilitate linking it with the client. We also used `--net` option to attach the container to our prepared network.
42
42
As mentioned before, you can have multiple instances of the Memcached server, just remember to give each of them a unique name. For example, the following commands create four Memcached server instances:
To start the client you have to first `pull` the client image and then run it. To `pull` the server image use the following command:
52
52
53
-
$ docker pull cloudsuite/data-caching:client
53
+
$ docker pull cloudsuite3/data-caching:client
54
54
55
55
It takes some time to download the image, but this is only required the first time.
56
56
57
57
To start the client container use the following command:
58
58
59
-
$ docker run -it --name dc-client --net caching_network cloudsuite/data-caching:client bash
59
+
$ docker run -it --name dc-client --net caching_network cloudsuite3/data-caching:client bash
60
60
61
61
This boots up the client container and you'll be logged in as the `memcache` user. Note that by using the `--net` option, you can easily make these containers visible to each other.
62
62
@@ -133,11 +133,11 @@ and the client on different sockets of the same machine
Copy file name to clipboardExpand all lines: docs/benchmarks/data-serving.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,22 +21,22 @@ We will attach the launched containers to this newly created docker network.
21
21
Start the server container that will run cassandra server and installs a default keyspace usertable:
22
22
23
23
```bash
24
-
$ docker run --name cassandra-server --net serving_network cloudsuite/data-serving:server cassandra
24
+
$ docker run --name cassandra-server --net serving_network cloudsuite3/data-serving:server cassandra
25
25
```
26
26
### Multiple Server Containers
27
27
28
28
For a cluster setup with multiple servers, we need to instantiate a seed server:
29
29
30
30
```bash
31
-
$ docker run --name cassandra-server-seed --net serving_network cloudsuite/data-serving:server
31
+
$ docker run --name cassandra-server-seed --net serving_network cloudsuite3/data-serving:server
32
32
```
33
33
34
34
Then we prepare the server as previously.
35
35
36
36
The other server containers are instantiated as follows:
37
37
38
38
```bash
39
-
$ docker run --name cassandra-server(id) --net serving_network -e CASSANDRA_SEEDS=cassandra-server-seed cloudsuite/data-serving:server
39
+
$ docker run --name cassandra-server(id) --net serving_network -e CASSANDRA_SEEDS=cassandra-server-seed cloudsuite3/data-serving:server
40
40
```
41
41
42
42
You can find more details at the websites: http://wiki.apache.org/cassandra/GettingStarted and https://hub.docker.com/_/cassandra/.
@@ -46,7 +46,7 @@ After successfully creating the aforementioned schema, you are ready to benchmar
46
46
Start the client container specifying server name(s), or IP address(es), separated with commas, as the last command argument:
47
47
48
48
```bash
49
-
$ docker run --name cassandra-client --net serving_network cloudsuite/data-serving:client "cassandra-server-seed,cassandra-server1"
49
+
$ docker run --name cassandra-client --net serving_network cloudsuite3/data-serving:client "cassandra-server-seed,cassandra-server1"
50
50
```
51
51
52
52
More detailed instructions on generating the dataset can be found in Step 5 at [this](http://github.com/brianfrankcooper/YCSB/wiki/Running-a-Workload) link. Although Step 5 in the link describes the data loading procedure, other steps (e.g., 1, 2, 3, 4) are very useful to understand the YCSB settings.
@@ -71,9 +71,9 @@ Running the benchmark
71
71
---------------------
72
72
The benchmark is run automatically with the client container. One can modify the record count in the database and/or the number of operations performed by the benchmark specifying the corresponding variables when running the client container:
0 commit comments