evio | Fast event-loop networking for Go | Networking library

by tidwall Go Version: v1.0.8 License: MIT

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

kandi X-RAY | evio Summary

evio is a Go library typically used in Networking applications. evio has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

evio is an event loop networking framework that is fast and small. It makes direct epoll and kqueue syscalls rather than using the standard Go net package, and works in a similar manner as libuv and libevent. The goal of this project is to create a server framework for Go that performs on par with Redis and Haproxy for packet handling. It was built to be the foundation for Tile38 and a future L7 proxy for Go.

Support

Quality

Security

License

Reuse

Support

evio has a medium active ecosystem.

It has 5637 star(s) with 481 fork(s). There are 172 watchers for this library.

It had no major release in the last 6 months.

There are 19 open issues and 36 have been closed. On average issues are closed in 42 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of evio is v1.0.8

Quality

evio has 0 bugs and 0 code smells.

Security

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

evio code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

evio is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

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

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of evio

Get all kandi verified functions for this library.

evio Key Features

No Key Features are available at this moment for evio.

evio Examples and Code Snippets

No Code Snippets are available at this moment for evio.

Community Discussions

Trending Discussions on evio

Go Evio application suddenly does not respond. Profiling shows all threads have stopped

Config nginx to reverse proxy for mqtt communication

Weird timeout from ev_timer

QUESTION

Go Evio application suddenly does not respond. Profiling shows all threads have stopped

Asked 2021-Apr-22 at 13:35

We have an application based on Evio in docker. When running some network load tests we can see that all threads suddenly dropped, heap is flushed. After few seconds timeout it continues execution as usual. App itself was not restarted, but all Evio threads were dead for ~5 seconds.

What can cause this behavior?

Config:

...

ANSWER

Answered 2021-Apr-22 at 13:35

Issue was not in Evio or Go profiling. After more investigation it became clear that all routines are blocked by external service. In our case that was gRPC connection in blocking mode, where other instance was not capable in handling such amount of requests.

This video also can be helpful. It shows similar symptoms and how to analyze them. https://www.youtube.com/watch?v=V74JnrGTwKA

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

QUESTION

Config nginx to reverse proxy for mqtt communication

Asked 2020-Dec-07 at 09:36

I have an MQTT (EMQX) server running on an ip and a port. And I communicate directly between my service and that port using the nodejs MQTT library.

I want to use a reverse proxy (nginx) to be able to use a DNS in order to prune the communication.

At this moment my nginx is configured like this:

...

ANSWER

Answered 2020-Dec-05 at 11:59

As hashed out in the comments.

The problem here was that the 2 services were being started from seperate docker-compose files. While they were both binding to networks with the same name, those networks were separate because they were being prefixed by different orchestration names.

There are 2 solutions to this problem:

Combine the 2 docker compose files, this will mean that they are then in the same namespace and will share the common named network.
Create a "external" network and reference this from both files.

For the second option you use the docker network command to create the network, e.g. docker network create evio_network and then at the end of each compose file include the following:

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

QUESTION

Weird timeout from ev_timer

Asked 2020-May-25 at 01:15

Recently I was trying code libev with threads I just noticed timer always ends at near 60~ second no matter what you set it lower than 60 second. I'm not sure what causes it but I tried make code shortest possible.

1 - Call some io_init and io_start

2 - Create new thread that will call ev_loop

3 - Create timer with 5 second timeout

4 - Wait for thread to finish then main function ends

...

ANSWER

Answered 2020-May-25 at 01:15

We needed to implement thread mutexes or libev's ev_async functions. Here is example code that using ev_async

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

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

Vulnerabilities

No vulnerabilities reported

Install evio

You can download it from GitHub.

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: