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

When the build does not produce any output, the elapsed time can be sluggish #224

Closed
gnodet opened this issue Nov 16, 2020 · 3 comments
Closed
Assignees
Milestone

Comments

@gnodet
Copy link
Contributor

gnodet commented Nov 16, 2020

No description provided.

@ppalaga
Copy link
Contributor

ppalaga commented Nov 16, 2020

Well, as long as the client is connected with the daemon, the KEEP_ALIVE messages keep the elapsed time to be updated. Yes, it is slugish while starting a new daemon. Or you have some other situation in mind?

@gnodet gnodet self-assigned this Nov 16, 2020
@gnodet
Copy link
Contributor Author

gnodet commented Nov 16, 2020

It's just the clock which is not really regular, so I'd like to lower the keep-alive time to 100ms so that the clock is updated regularly and not every 1.5s for example. This should not cause too much additional traffic given the size of the message and given the client is simply waiting for any message to come in.

@ppalaga
Copy link
Contributor

ppalaga commented Nov 16, 2020

Ah, I see what you mean now. I have not observed that, perhaps because I am on a powerful machine with enough reserves to schedule the terminal updates on time. Yeah, KEEP_ALIVEs every 100ms is worth trying.

gnodet added a commit to gnodet/mvnd that referenced this issue Nov 16, 2020
gnodet added a commit to gnodet/mvnd that referenced this issue Nov 16, 2020
@gnodet gnodet closed this as completed in cf5c512 Nov 16, 2020
@ppalaga ppalaga added this to the 0.0.13 milestone Nov 17, 2020
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

2 participants