Skip to content

Asynchronous threaded support for senders and handlers. #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 10, 2017

Conversation

panta
Copy link
Contributor

@panta panta commented Nov 7, 2017

These decouple the logging from the actual sending, which is delegated to a separate dedicated thread.
This is useful in high-speed applications, where the network overhead is not (always) acceptable.
This also avoids the issues of the logging server not being reachable and leading to timeouts, with the corresponding huge slowdowns.

The asynchronous versions are entirely optional.
Full test suites are provided.

These are implemented respectively in asyncsender and asynchandler, with the same interfaces as their synchronous counterparts.
@coveralls
Copy link

coveralls commented Nov 7, 2017

Coverage Status

Coverage increased (+0.04%) to 90.909% when pulling d9a7ab6 on panta:feature/asynchronous-communication into 0efc2fc on fluent:master.

1 similar comment
@coveralls
Copy link

coveralls commented Nov 7, 2017

Coverage Status

Coverage increased (+0.04%) to 90.909% when pulling d9a7ab6 on panta:feature/asynchronous-communication into 0efc2fc on fluent:master.

@repeatedly
Copy link
Member

repeatedly commented Nov 9, 2017

Could you update README about this feature?

@repeatedly repeatedly self-assigned this Nov 9, 2017
…same interface as the regular handler module.
@coveralls
Copy link

coveralls commented Nov 9, 2017

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling e66e4e3 on panta:feature/asynchronous-communication into 0efc2fc on fluent:master.

@coveralls
Copy link

coveralls commented Nov 9, 2017

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling d920d71 on panta:feature/asynchronous-communication into 0efc2fc on fluent:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling d920d71 on panta:feature/asynchronous-communication into 0efc2fc on fluent:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling d920d71 on panta:feature/asynchronous-communication into 0efc2fc on fluent:master.

@panta panta force-pushed the feature/asynchronous-communication branch from 3a3e97b to 25ecbda Compare November 9, 2017 08:19
@coveralls
Copy link

coveralls commented Nov 9, 2017

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling 25ecbda on panta:feature/asynchronous-communication into 66603f2 on fluent:master.

@panta
Copy link
Contributor Author

panta commented Nov 9, 2017

I've updated the README, and also fixed an issue that made the communication thread heavy on the CPU.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling 25ecbda on panta:feature/asynchronous-communication into 66603f2 on fluent:master.

3 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling 25ecbda on panta:feature/asynchronous-communication into 66603f2 on fluent:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling 25ecbda on panta:feature/asynchronous-communication into 66603f2 on fluent:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 91.212% when pulling 25ecbda on panta:feature/asynchronous-communication into 66603f2 on fluent:master.

@repeatedly repeatedly merged commit 0d10c47 into fluent:master Nov 10, 2017
@repeatedly
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants