2009-08-30 15:03:16 +02:00
|
|
|
/*
|
2016-01-28 15:07:31 +01:00
|
|
|
Copyright (c) 2007-2016 Contributors as noted in the AUTHORS file
|
2009-08-30 15:03:16 +02:00
|
|
|
|
2015-06-02 22:33:55 +02:00
|
|
|
This file is part of libzmq, the ZeroMQ core engine in C++.
|
2009-08-30 15:03:16 +02:00
|
|
|
|
2015-06-02 22:33:55 +02:00
|
|
|
libzmq is free software; you can redistribute it and/or modify it under
|
|
|
|
the terms of the GNU Lesser General Public License (LGPL) as published
|
|
|
|
by the Free Software Foundation; either version 3 of the License, or
|
2009-08-30 15:03:16 +02:00
|
|
|
(at your option) any later version.
|
|
|
|
|
2015-06-02 22:33:55 +02:00
|
|
|
As a special exception, the Contributors give you permission to link
|
|
|
|
this library with independent modules to produce an executable,
|
|
|
|
regardless of the license terms of these independent modules, and to
|
|
|
|
copy and distribute the resulting executable under terms of your choice,
|
|
|
|
provided that you also meet, for each linked independent module, the
|
|
|
|
terms and conditions of the license of that module. An independent
|
|
|
|
module is a module which is not derived from or based on this library.
|
|
|
|
If you modify this library, you must extend this exception to your
|
|
|
|
version of the library.
|
|
|
|
|
|
|
|
libzmq is distributed in the hope that it will be useful, but WITHOUT
|
|
|
|
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
|
|
|
|
FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public
|
|
|
|
License for more details.
|
2009-08-30 15:03:16 +02:00
|
|
|
|
2010-10-30 15:08:28 +02:00
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
2009-08-30 15:03:16 +02:00
|
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
2013-03-03 15:28:00 +08:00
|
|
|
#include "../include/zmq.h"
|
2009-08-30 15:03:16 +02:00
|
|
|
#include <stdio.h>
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
2017-08-10 14:29:21 -04:00
|
|
|
// keys are arbitrary but must match remote_lat.cpp
|
|
|
|
const char server_prvkey[] = "{X}#>t#jRGaQ}gMhv=30r(Mw+87YGs+5%kh=i@f8";
|
|
|
|
|
2009-08-30 15:03:16 +02:00
|
|
|
int main (int argc, char *argv[])
|
|
|
|
{
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
const char *bind_to;
|
|
|
|
int message_count;
|
|
|
|
size_t message_size;
|
2013-02-26 12:10:27 -08:00
|
|
|
void *ctx;
|
|
|
|
void *s;
|
|
|
|
int rc;
|
|
|
|
int i;
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
zmq_msg_t msg;
|
|
|
|
void *watch;
|
|
|
|
unsigned long elapsed;
|
2017-08-10 14:30:22 -04:00
|
|
|
double throughput;
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
double megabits;
|
2017-08-10 14:29:21 -04:00
|
|
|
int curve = 0;
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
|
2017-08-10 14:29:21 -04:00
|
|
|
if (argc != 4 && argc != 5) {
|
|
|
|
printf ("usage: local_thr <bind-to> <message-size> <message-count> "
|
|
|
|
"[<enable_curve>]\n");
|
2009-08-30 15:03:16 +02:00
|
|
|
return 1;
|
|
|
|
}
|
2013-02-26 12:10:27 -08:00
|
|
|
bind_to = argv[1];
|
|
|
|
message_size = atoi (argv[2]);
|
|
|
|
message_count = atoi (argv[3]);
|
2017-08-10 14:29:21 -04:00
|
|
|
if (argc >= 5 && atoi (argv[4])) {
|
|
|
|
curve = 1;
|
|
|
|
}
|
2013-02-26 12:10:27 -08:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
ctx = zmq_init (1);
|
2010-01-18 15:57:33 +01:00
|
|
|
if (!ctx) {
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
printf ("error in zmq_init: %s\n", zmq_strerror (errno));
|
2010-01-18 15:57:33 +01:00
|
|
|
return -1;
|
|
|
|
}
|
2009-08-30 15:03:16 +02:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
s = zmq_socket (ctx, ZMQ_PULL);
|
2010-01-18 15:57:33 +01:00
|
|
|
if (!s) {
|
|
|
|
printf ("error in zmq_socket: %s\n", zmq_strerror (errno));
|
|
|
|
return -1;
|
|
|
|
}
|
2009-09-16 12:22:36 +02:00
|
|
|
|
|
|
|
// Add your socket options here.
|
|
|
|
// For example ZMQ_RATE, ZMQ_RECOVERY_IVL and ZMQ_MCAST_LOOP for PGM.
|
2017-08-10 14:29:21 -04:00
|
|
|
if (curve) {
|
|
|
|
rc = zmq_setsockopt (s, ZMQ_CURVE_SECRETKEY, server_prvkey,
|
|
|
|
sizeof (server_prvkey));
|
|
|
|
if (rc != 0) {
|
|
|
|
printf ("error in zmq_setsockoopt: %s\n", zmq_strerror (errno));
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
int server = 1;
|
|
|
|
rc = zmq_setsockopt (s, ZMQ_CURVE_SERVER, &server, sizeof (int));
|
|
|
|
if (rc != 0) {
|
|
|
|
printf ("error in zmq_setsockoopt: %s\n", zmq_strerror (errno));
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
}
|
2009-09-16 12:22:36 +02:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
rc = zmq_bind (s, bind_to);
|
2013-02-26 12:10:27 -08:00
|
|
|
if (rc != 0) {
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
printf ("error in zmq_bind: %s\n", zmq_strerror (errno));
|
2010-01-18 15:57:33 +01:00
|
|
|
return -1;
|
|
|
|
}
|
2009-08-30 15:03:16 +02:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
rc = zmq_msg_init (&msg);
|
2010-01-18 15:57:33 +01:00
|
|
|
if (rc != 0) {
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
printf ("error in zmq_msg_init: %s\n", zmq_strerror (errno));
|
2010-01-18 15:57:33 +01:00
|
|
|
return -1;
|
|
|
|
}
|
2009-08-30 15:03:16 +02:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
rc = zmq_recvmsg (s, &msg, 0);
|
|
|
|
if (rc < 0) {
|
|
|
|
printf ("error in zmq_recvmsg: %s\n", zmq_strerror (errno));
|
2010-01-18 15:57:33 +01:00
|
|
|
return -1;
|
|
|
|
}
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
if (zmq_msg_size (&msg) != message_size) {
|
|
|
|
printf ("message of incorrect size received\n");
|
2010-01-18 15:57:33 +01:00
|
|
|
return -1;
|
|
|
|
}
|
2009-08-30 15:03:16 +02:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
watch = zmq_stopwatch_start ();
|
2009-08-30 15:03:16 +02:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
for (i = 0; i != message_count - 1; i++) {
|
|
|
|
rc = zmq_recvmsg (s, &msg, 0);
|
|
|
|
if (rc < 0) {
|
|
|
|
printf ("error in zmq_recvmsg: %s\n", zmq_strerror (errno));
|
2010-01-18 15:57:33 +01:00
|
|
|
return -1;
|
|
|
|
}
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
if (zmq_msg_size (&msg) != message_size) {
|
|
|
|
printf ("message of incorrect size received\n");
|
2013-02-26 12:10:27 -08:00
|
|
|
return -1;
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
}
|
2009-08-30 15:03:16 +02:00
|
|
|
}
|
2013-02-26 12:10:27 -08:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
elapsed = zmq_stopwatch_stop (watch);
|
|
|
|
if (elapsed == 0)
|
|
|
|
elapsed = 1;
|
2013-02-26 12:10:27 -08:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
rc = zmq_msg_close (&msg);
|
|
|
|
if (rc != 0) {
|
|
|
|
printf ("error in zmq_msg_close: %s\n", zmq_strerror (errno));
|
|
|
|
return -1;
|
2010-01-18 15:57:33 +01:00
|
|
|
}
|
2009-11-26 12:01:26 +01:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
throughput = ((double) message_count / (double) elapsed * 1000000);
|
2016-02-03 19:00:51 +06:00
|
|
|
megabits = ((double) throughput * message_size * 8) / 1000000;
|
2009-08-30 15:03:16 +02:00
|
|
|
|
I'm reverting the various changes to the throughput test programs since as far
as I can see, these didn't work any more. At the very least, the command line
API was broken and forced the user to enter new, exotic arguments. Patches
should not break existing APIs. But also, the internals of these programs had
become weird.
If we want to build more complex performance tests, that's fine, but we should
make new programs, not break the old ones. We need minimal, safe performance
tests in 0MQ.
Also, the code was quite horrid. So it's gone. If anyone wants to bring it back
please make the code neat, and build new APIs instead of breaking the old ones.
Cheers
Pieter
2013-04-15 17:18:03 +02:00
|
|
|
printf ("message size: %d [B]\n", (int) message_size);
|
|
|
|
printf ("message count: %d\n", (int) message_count);
|
|
|
|
printf ("mean throughput: %d [msg/s]\n", (int) throughput);
|
|
|
|
printf ("mean throughput: %.3f [Mb/s]\n", (double) megabits);
|
2009-09-02 14:59:53 +02:00
|
|
|
|
2009-09-04 16:02:41 +02:00
|
|
|
rc = zmq_close (s);
|
2010-01-18 15:57:33 +01:00
|
|
|
if (rc != 0) {
|
|
|
|
printf ("error in zmq_close: %s\n", zmq_strerror (errno));
|
|
|
|
return -1;
|
|
|
|
}
|
2009-09-04 16:02:41 +02:00
|
|
|
|
2016-02-01 23:00:06 +01:00
|
|
|
rc = zmq_ctx_term (ctx);
|
2010-01-18 15:57:33 +01:00
|
|
|
if (rc != 0) {
|
2016-02-01 23:00:06 +01:00
|
|
|
printf ("error in zmq_ctx_term: %s\n", zmq_strerror (errno));
|
2010-01-18 15:57:33 +01:00
|
|
|
return -1;
|
|
|
|
}
|
2009-08-30 15:03:16 +02:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|