reproxy | Reverse http proxy | Proxy library

by fulldump Go Version: 0.0.8 License: Non-SPDX

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

kandi X-RAY | reproxy Summary

reproxy is a Go library typically used in Networking, Proxy applications. reproxy has no bugs, it has no vulnerabilities and it has low support. However reproxy has a Non-SPDX License. You can download it from GitHub.

Reverse http proxy

Support

Quality

Security

License

Reuse

Support

reproxy has a low active ecosystem.

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

It had no major release in the last 12 months.

There are 2 open issues and 1 have been closed. On average issues are closed in 14 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of reproxy is 0.0.8

Quality

reproxy has no bugs reported.

Security

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

License

reproxy has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

reproxy releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

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

type script
type proxy
All proxy types
Set a new entry
NewReproxy creates a new reproxy api
generate go code
save to disk
Create a config file
Get returns the current configuration
Load reads a file

Get all kandi verified functions for this library.

reproxy Key Features

No Key Features are available at this moment for reproxy.

reproxy Examples and Code Snippets

Reproxy,Getting started

Lines of Code : 3

License : Non-SPDX (NOASSERTION)

Copy

./reproxy 

./reproxy --address=9000

./reproxy --filename=other_file.json

Reproxy,Reproxy developer,Build

Lines of Code : 2

License : Non-SPDX (NOASSERTION)

Copy

make

make build_all

Reproxy,Reproxy developer,Static files

Lines of Code : 1

License : Non-SPDX (NOASSERTION)

Copy

go run src/genstatic/genstatic.go --dir=static/ --package=files > src/reproxy/files/data.go

Community Discussions

Trending Discussions on reproxy

Network performance issues and slow tcp_write_xmit/tcp_ack syscalls with a lot of save_stack calls on OpenVZ kernel

QUESTION

Network performance issues and slow tcp_write_xmit/tcp_ack syscalls with a lot of save_stack calls on OpenVZ kernel

Asked 2018-Jan-25 at 09:51

I ran into a trouble with a bad network performance on Centos. The issue was observed on the latest OpenVZ RHEL7 kernel (3.10 based) on Dell server with 24 cores and Broadcom 5720 NIC. No matter it was host system or OpenVZ container. Server receives RTMP connections and reproxy RTMP streams to another consumers. Reads and writes was unstable and streams froze periodically for few seconds.

I've started to check system with strace and perf. Strace affects system heavily and seems that only perf may help. I've used OpenVZ debug kernel with debugfs enabled. System spends too much time in swapper process (according to perf data). I've built flame graph for the system under the load (100mbit in data, 200 mbit out) and have noticed that kernel spent too much time in tcp_write_xmit and tcp_ack. On the top of these calls I see save_stack syscalls.

On another hand, I tested the same scenario on Amazon EC2 instance (latest Amazon Linux AMI 2017.09) and perf doesn't track such issues. Total amount of samples was 300000, system spends 82% of time according to perf samples in swapper, but net_rx_action (and as consequent tcp_write_xmit and tcp_ack) in swapper takes only 1797 samples (0.59% of total amount of samples). On the top of net_rx_action call in flame graph I don't see any calls related to stack traces.

Output of OpenVZ system looks differently. Among 1833152 samples 500892 (27%) was in swapper process, 194289 samples (10.5%) was in net_rx_action.

Full svg of calls on vzkernel7 is here and svg of EC2 instance calls is here. You may download it and open in browser to interactively check flame graph.

So, I want to ask for help and I have few questions.

Why flame graph from EC2 instance doesn't contain so much save_stack calls like my server?
Does perf forces system to call save_stack or it's some kernel setting? May it be disabled and how?
Does Xen on EC2 guest process all tcp_ack and other syscalls? Is it possible that host system on EC2 server makes some job and guest system doesn't see it?

Thank you for a help.

...

ANSWER

Answered 2018-Jan-25 at 09:51

I've read kernel sources and have an answer for my questions.

save_stack calls is caused by the Kernel Address Sanitizer feature that was enabled in OpenVZ debug kernel by CONFIG_KASAN option. When this options is enabled, on each kmem_cache_free syscall kernel calls __cache_free

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

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

Vulnerabilities

No vulnerabilities reported

Install reproxy

Open http://localhost:8000/reproxy/ and configure it.
How to build for all architectures:.

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: