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

Autoscaling & Performance tracking #269

Open
mattdonnelly10 opened this issue Sep 19, 2024 · 2 comments
Open

Autoscaling & Performance tracking #269

mattdonnelly10 opened this issue Sep 19, 2024 · 2 comments

Comments

@mattdonnelly10
Copy link

Is there a cloud autoscaling configuration for Fishnet yet, such as K8s HPA or KEDA? Also, is there an official way to collect container logs to track how many games/positions you've analyzed across containers? When run on the desktop, I get the stats in a json file, but with containers there is just the stdout logs.

@niklasf
Copy link
Member

niklasf commented Sep 22, 2024

Hi. There's currently no off-the-shelf autoscaling. I've seen two successful ways to do it:

The stats file is off by default in containers, but can be enabled with the STATS_FILE environment variable (see docker-entrypoint.sh). We could also consider exposing stats in other/additional ways, if you have suggestions.

@mattdonnelly10
Copy link
Author

Thanks, enabling the stats file was a good suggestion, but I decided to just use Promtail, Loki, and Grafana to track all the stats. For the auto-scaling, I used the http-json Prometheus exporter to scrape the queue metrics and then a Kubernetes HPA to auto-scale containers as the queue changes.

Link here in case anyone finds this issue looking for something similar:
https://github.com/mattdonnelly10/fishwatch

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