[ 
https://issues.apache.org/jira/browse/SSHD-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983257#comment-15983257
 ] 

Goldstein Lyor commented on SSHD-742:
-------------------------------------

You have not wasted time - it's just that the issue was not clearly stated. In 
any case
{quote}
A request is relatively small (around 200 bytes). On the other hand, the 
response might be around 8 to 10 KB.
{quote}
IMO, SSH is not built for "requests" but rather for long-lived sessions, since 
it has quite an overhead in the initial session establishment as well as the 
whole encryption mechanism. In any case, if you do want to "compare" it to an 
HTTP-like mechanism, the closest you can get is to use *HTTPS* and ensure that 
you are not using the {{Keep-Alive}} option or any session re-use. Even then, I 
agree with [~gnt] that it would still be equivalent to comparing apples and 
oranges.

> Are there any ways to improve performance?
> ------------------------------------------
>
>                 Key: SSHD-742
>                 URL: https://issues.apache.org/jira/browse/SSHD-742
>             Project: MINA SSHD
>          Issue Type: Question
>    Affects Versions: 1.4.0
>         Environment: https://github.com/maseev/sshd-echo
>            Reporter: Miron Aseev
>            Priority: Minor
>
> I created a simple client-server application (see the environment section) 
> that uses MINA SSHD library, just to test the performance. I was quite 
> disappointed because the throughput was particularly low - 2400 requests per 
> second on average on localhost.
> According to Java Flight Recorder, the application spends most of its time in 
> ChannelPipedInputStream/ChannelPipedOutputStream on different monitor objects.
> Is there any way I can improve the performance? The documentation is kinda 
> sparse and doesn't mention any tuning suggestions. Maybe I can avoid using 
> these piped streams somehow or set some parameters related to the transport 
> layer?
> All suggestions are greatly appreciated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to