-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use the Canonical Project Structure for Broker
For the Canonical Project Structure, see https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1204r0.html. With the new structure, we drop the `include` and `src` sub-directories and place the source files next to the header files under `libbroker`. Further, we place the unit tests next to the source file with `.test.cc` suffix. Standalone tools have been placed alongside `libbroker` to the project root, whereas system/integration tests as well as benchmarks remain under `tests`, but are organized more consistently.
- Loading branch information
Showing
327 changed files
with
410 additions
and
1,054 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
add_executable(broker-node | ||
broker-node.cc | ||
) | ||
target_link_libraries(broker-node PRIVATE ${BROKER_LIBRARY} CAF::core) | ||
target_include_directories(broker-node PRIVATE | ||
"${CMAKE_CURRENT_SOURCE_DIR}" | ||
"${CMAKE_CURRENT_BINARY_DIR}") |
File renamed without changes.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
add_executable(broker-pipe | ||
broker-pipe.cc | ||
) | ||
target_link_libraries(broker-pipe PRIVATE ${BROKER_LIBRARY} CAF::core) | ||
target_include_directories(broker-pipe PRIVATE | ||
"${CMAKE_CURRENT_SOURCE_DIR}" | ||
"${CMAKE_CURRENT_BINARY_DIR}") |
File renamed without changes.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
add_executable(broker-throughput | ||
broker-throughput.cc | ||
) | ||
target_link_libraries(broker-throughput PRIVATE ${BROKER_LIBRARY}) | ||
target_include_directories(broker-throughput PRIVATE | ||
"${CMAKE_CURRENT_SOURCE_DIR}" | ||
"${CMAKE_CURRENT_BINARY_DIR}") |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
The utility program `broker-throughput` is a standalone tool to measure the | ||
throughput of a network of Broker endpoints. | ||
|
||
A test setup requires at least two processes: a client and a server. | ||
|
||
### Starting the Server | ||
|
||
The server simply creates a Broker endpoint and binds it to the given port: | ||
|
||
```sh | ||
broker-throughput --verbose --server :8080 | ||
``` | ||
|
||
### Staring the Client | ||
|
||
After starting the server, clients can start peering to it. The important | ||
parameters of the benchmark are message type (`-t`) and rate (`-r`). The | ||
message type is 1 for trivial strings, 2 for Broker vectors that resemble a | ||
line in conn.log, or 3 for large Broker tables. The rate parameter configures | ||
how many messages per second the client should send. | ||
|
||
For sending 1,000 large table messages per second, the client could get started | ||
as follows: | ||
|
||
```sh | ||
broker-throughput --verbose -t 3 -r 1000 localhost:8080 | ||
``` |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
Oops, something went wrong.