tcping | An RTT measurement tool written in Python | Download Utils library

by oraccha Python Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | tcping Summary

tcping is a Python library typically used in Utilities, Download Utils applications. tcping has no bugs, it has no vulnerabilities and it has low support. However tcping build file is not available. You can download it from GitHub.

tcping: a simple RTT measurement tool written in Python. Copyright (C) 2009 oraccha

Support

Quality

Security

License

Reuse

Support

tcping has a low active ecosystem.

It has 7 star(s) with 5 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

tcping has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of tcping is current.

Quality

tcping has 0 bugs and 0 code smells.

Security

tcping has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

tcping code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

tcping does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

tcping releases are not available. You will need to build from source code and install.

tcping has no build file. You will be need to create the build yourself to build the component from source.

It has 85 lines of code, 3 functions and 2 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed tcping and discovered the below as its top functions. This is intended to give you an instant insight into tcping implemented functionality, and help decide if they suit your requirements.

Start tcping
Start tcping daemon
Calculate mean squared of a list of values .

Get all kandi verified functions for this library.

tcping Key Features

No Key Features are available at this moment for tcping.

tcping Examples and Code Snippets

No Code Snippets are available at this moment for tcping.

Community Discussions

Trending Discussions on tcping

Why is there a discrepancy between python sockets and tcp ping for the same IP:port destination?

QUESTION

Why is there a discrepancy between python sockets and tcp ping for the same IP:port destination?

Asked 2021-Apr-02 at 13:36

My setup:

I am using an IP and port provided by portmap.io to allow me to perform port forwarding.
I have OpenVPN installed (as required by portmap.io), and I run a ready-made config file when I want to operate my project.
My main effort involves sending messages between a client and a server using sockets in Python.
I have installed a software called tcping, which basically allows me to ping an IP:port over a tcp connection.

This figure basically sums it up:

Results I'm getting:

When I try to "ping" said IP, the average RTT ends up being around 30ms consistently.
I try to use the same IP to program sockets in Python, where I have a server script on my machine running, and a client script on any other machine but binding to this IP. I try sending a small message like "Hello" over the socket, and I am finding that the message is taking a significantly greater amount of time to travel across, and an inconsistent one for that matter. Sometimes it ends up taking 1 second, sometimes 400ms...

What is the reason for this discrepancy?

...

ANSWER

Answered 2021-Apr-02 at 13:36

What is the reason for this discrepancy?

tcpping just measures the time needed to establish the TCP connection. The connection establishment is usually completely done in the OS kernel, so there is not even a switch to user space involved.

Even some small data exchange at the application is significantly more expensive. First, the initial TCP handshake must be done. Usually only once the TCP handshake is done the client starts sending the payload, which then needs to be delivered to the other side, put into the sockets read buffer, schedule the user space application to run, read the data from the buffer in the application and process, create and deliver the response to the peers OS kernel, let the kernel deliver the response to the local system and lots of stuff here too until the local app finally gets the response and ends the timing of how long this takes.

Given that the time for the last one is that much off from the pure RTT I would assume though that the server system has either low performance or high load or that the application is written badly.

Source https://stackoverflow.com/questions/66917417

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install tcping

You can download it from GitHub.
You can use tcping like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: