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

Support millisecond granularity in logs #10

Open
optix2000 opened this issue Sep 15, 2015 · 3 comments
Open

Support millisecond granularity in logs #10

optix2000 opened this issue Sep 15, 2015 · 3 comments

Comments

@optix2000
Copy link

Looks like timestamps are converted to longs. At high request rates (100+ QPS), this causes batches of balls to get sent every second instead of as a stream. This not only ruins the effect, but also causes lag as hundreds of balls are rendered in batches.

@bentcoder
Copy link

bentcoder commented Jan 5, 2018

Same here. Instead of throwing the balls continuously as soon as they hit the log file, Logstalgia seems to be storing them as in batches and throws them all in one go every 10ish seconds - (a bit worse than "every second" in like @optix2000 described above).

@optix2000 Have you found a solution yet?

@bentcoder
Copy link

@acaudwell Is there a fix for this issue?

@acaudwell
Copy link
Owner

10 seconds sounds like there is external buffering going on before they reach Logstalgia so I'd look into that. For instance some commands will buffer by default and you need to change a setting to flush immediately. Logstalgia linearly distributes the release of the last seconds requests in the order they were received so you shouldn't see that kind of delay.

Maybe also try the --sync option if you're not using that.

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

No branches or pull requests

3 participants