The only common process between the n worker processes is the database. When one asks for the same repo n times we will do the same task n times.
This gets even worse as we do not have any caching or rate limiting.
A simple solution would be to use a single worker.
The only common process between the $n$ worker processes is the database. When one asks for the same repo $n$ times we will do the same task $n$ times.
This gets even worse as we do not have __any__ caching or rate limiting.
A simple solution would be to use a single worker.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The only common process between the
nworker processes is the database. When one asks for the same repontimes we will do the same taskntimes.This gets even worse as we do not have any caching or rate limiting.
A simple solution would be to use a single worker.