Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL/TLS slowness #70

Open
phr0gz opened this issue Jun 1, 2017 · 2 comments
Open

SSL/TLS slowness #70

phr0gz opened this issue Jun 1, 2017 · 2 comments
Assignees

Comments

@phr0gz
Copy link

phr0gz commented Jun 1, 2017

Hello, it seems that the SSL/TLS option is slowing down the input packet rate, I've done two tests:

1/ Test 1

In this test there are two computers:

Computer1 with rsyslog
Computer2 with logstash (In this test logstash is running with ssl_enable => "true")

Computer1 is sending data with rsyslog via rsyslog-tls to Computer2 with logstash.

Schema:

computer1 (rSyslog) ---TLS---> Computer2 (Logstash)

2/ Test 2

In this test there are two computers:

Computer1 with rsyslog
Computer2 with rsyslog and logstash

Computer1 is sending data with rsyslog via rsyslog-tls to Computer2, Computer2 receive the encrypted data with rsyslog, decrypt the data and send it to logstash via the loopback.

Schema:

computer1 (rSyslog) ---TLS---> Computer2 (rSyslog ---No TLS---> Logstash)

Condition of the test:

Step1:

Computer1 is overloaded with logger during 30 minutes (logs are stored in the RAM).

Step2:

Then the service(s) is/are started on Computer2: for test1 logstash; for test2 logstash and rsyslog.

Result:

Test1:

test1

Test2:

test2

As we can see in Test1 we receive 2000 events/sec, but in Test2 we receive 20000 event/s.
We can't say it's because decoding TLS is taking a lot of resources, because in the second test we are using rsyslog on the same machine as logstash (sort of ssl offloading via rsyslog).

@phr0gz
Copy link
Author

phr0gz commented Jun 2, 2017

OS: Redhat 7
Logstash: 5.4.0

@original-brownbear original-brownbear self-assigned this Jun 23, 2017
@original-brownbear
Copy link
Contributor

@suyograo @jordansissel will move the SSL path to Netty in this one.

@jakelandis ping for this one, I know you already did some work for this in the Beats input, we should sync up again on this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants