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

Allow to set a worker in a special mode which allows only requests where this worker is requested explicitely #71

Open
leszekhanusz opened this issue Nov 1, 2022 · 5 comments
Labels
enhancement New feature or request

Comments

@leszekhanusz
Copy link

I tried to see which power I could allow with my RTX3080 10GB with the inpainting model but if I start accepting requests for the horde, inevitably it starts generating images from other people and will crash if the image requested is too big.

For such experimentations, it would be nice if we could set the worker in a special mode where it would only accept request destined to this worker explicitely (if it is present in the workers field in the API)

@db0
Copy link
Member

db0 commented Nov 2, 2022

This goes against the spirit of the horde, It would allow people to host fake workers and not serve anything just to farm uptime kudos.

I'll see if we can set a temporary flag that can be set by horde moderators only and expires after 24h or something.

@leszekhanusz
Copy link
Author

You could simply stop generating kudos in this mode but we definitely need a way to test a worker independently.
IMHO asking moderators for this would be quite annoying. At the very least the possibility to test on localhost without contact with the horde at all.

@db0
Copy link
Member

db0 commented Nov 2, 2022

Oh ye why didn't I think of pausing kudos rewards. Good idea

@db0 db0 added the enhancement New feature or request label Nov 2, 2022
@db0
Copy link
Member

db0 commented Nov 2, 2022

It does leave open the possibility that someone will use the horde only for their own benefit (using it as a free networking). but I think we can try it out like this and deal with it later if it becomes a problem

@ndahlquist
Copy link
Contributor

Could we use maintenance mode for this? Actually, this is what I expected:

  1. I put my worker into maintenance mode, intending to perform stress testing and make sure the models perform correctly.
  2. I selected the "Use specific worker" in the web UI.

I intuitively expected that my jobs would still go to my worker under maintenance, but that seems to not be the case. Could we re-use that feature for this?

All-Ki pushed a commit to All-Ki/AI-Horde that referenced this issue Mar 7, 2023
All-Ki pushed a commit to All-Ki/AI-Horde that referenced this issue Mar 7, 2023
* Revert "Reload model database if we find an unknown model (Haidra-Org#46)"

This reverts commit cbb105a.

* Do correct spelling though.

* Adds unicode log support and kudos per hour stats.

* Lint fix

* We don't ALWAYS want to display kudos per hour.

* Add support for YAML configuration

* Lint fix

* Automatically convert existing py config to yaml.

* Convert webui to support YAML config

* Correctly bootstrap with no config files at all.

* Add support for "ALL MODELS" as a model name.

* Lint fix

* Ensure model-stats works with YAML config.

* models_to_skip also works when using "ALL MODELS"

* Update docs from bridgeData.py to bridgeData.yaml

* Lint fix

* Lint fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants