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
I know it is not a good practice to rename a tool, especially when there are lots of users are using it everyday.
Many people asked me questions that, ntttcp-for-linux actually is so different from the Windows version of ntttcp, why we still follow the name? Example of the difference is the tool options/usage. Keep such name (ntttcp-for-linux) would be confusing to some of us.
To be frankly, those are good questions. I am seriously considering to give a new name to this tool. For example, nspeed, or netspeed?
The text was updated successfully, but these errors were encountered:
I know it is not a good practice to rename a tool, especially when there are lots of users are using it everyday.
Many people asked me questions that, ntttcp-for-linux actually is so different from the Windows version of ntttcp, why we still follow the name? Example of the difference is the tool options/usage. Keep such name (ntttcp-for-linux) would be confusing to some of us.
To be frankly, those are good questions. I am seriously considering to give a new name to this tool. For example,
nspeed
, ornetspeed
?The text was updated successfully, but these errors were encountered: