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.

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

[BUG] Outbound message scheduler performance degradation #177

Open
Psychlist1972 opened this issue Dec 21, 2023 · 1 comment
Open

[BUG] Outbound message scheduler performance degradation #177

Psychlist1972 opened this issue Dec 21, 2023 · 1 comment
Assignees
Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. bug 🐞 Something isn't working

Comments

@Psychlist1972
Copy link
Contributor

Applies To
Outbound message scheduling

Describe the bug
Over a relatively short amount of time with sending messages, the scheduler performance degrades. This happens even after the queue has been drained and new messages are sent. It is especially evident in cases where the messages all have the same timestamp.

Easily reproducible by running the client TAEF tests and monitoring output. The delta between the expected receive time and the actual received time climbs into high milliseconds, and then even into seconds.

@Psychlist1972 Psychlist1972 added bug 🐞 Something isn't working area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. labels Dec 21, 2023
@Psychlist1972 Psychlist1972 self-assigned this Dec 21, 2023
@Psychlist1972
Copy link
Contributor Author

Note: This does appear to eventually lead to a service crash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. bug 🐞 Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant