Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Split processing and compression into separate stages #84

Open
darrylmasson opened this issue Apr 21, 2020 · 0 comments
Open

Split processing and compression into separate stages #84

darrylmasson opened this issue Apr 21, 2020 · 0 comments

Comments

@darrylmasson
Copy link
Collaborator

Redax uses "one" processing stage where a chunk of data from random digitizers is sent to a random thread for processing and compression. This makes tracking timestamp rollovers potentially more difficult, and also isn't the most effective way of load-balancing the CPU needs of processing and compression.

A better solution would be to split processing and compression into separate stages.
@darrylmasson darrylmasson mentioned this issue Sep 14, 2020
Closed
@darrylmasson darrylmasson linked a pull request Sep 14, 2020 that will close this issue
Redax 2.0 #99
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Redax 2.0 coderdj/redax
1 participant
@darrylmasson