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

Add option to reduce query frequency #6

Open
slater opened this issue Dec 25, 2024 · 3 comments
Open

Add option to reduce query frequency #6

slater opened this issue Dec 25, 2024 · 3 comments

Comments

@slater
Copy link

slater commented Dec 25, 2024

Right now, it's checking lightstreamer.com every second, and downloading a 1KB payload. Maybe have it query less often, or a preference to update manually, once an hour, etc.?

@bcardarella
Copy link

is the app downloading and parsing the site? If so can't you just connect to the websocket and tease out the correct value?

@Jaennaet
Copy link
Owner

The majority of that bandwidth is likely taken by the signal status subscription that was added for v0.2, as it's a field of the timestamp which is updated many times a second.

The metrics aren't parsed from any site, they come straight from the official public ISS metrics source. Unfortunately it's a push stream so we don't have any "clean" way of reducing the bandwidth, except maybe only subscribing to the timestamp thing periodically to update the LOS status but that doesn't sound very enticing

@Jaennaet
Copy link
Owner

Hrrrm I wonder if simply not subscribing to the TimeStamp field would help. I have no clue if Lightstreamer sends updates even if none of the fields in the update actually changed, or if they have a subscription mode that does that. Need to check their APIs; we're currently using the MERGE mode just because ISS-Mimic used it so I went with it. Cargo cult programming, yay ✈️

We don't currently check for stale data so we don't need the timestamp itself as such, just the status field (although if we ever do want to check staleness we would need it.)

I'll see if I have energy to look into this later today, it really is kind of annoying that we're using bandwidth for nothing – yeah the rate is pretty tiny in comparison, but it's annoying out of principle damnit

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