bruno-santos-6 commented on issue #23979:
URL: https://github.com/apache/superset/issues/23979#issuecomment-2361125814
> @AlexMSm I cannot speak to using cloud run, we are running it as a gke
cluster. When initiating the server something like this should work for a
simple case:
>
> ```
> gunicorn -w 10 -k gthread --timeout 180 -b
0.0.0.0:8080 --limit-request-line 0 --limit-request-field_size 0
"superset.app:create_app()" --daemon
> ```
>
> its the `-k` option where you specify the `gthread` option. I hope this
helps.
Hey, sir!
Could you share how you configured your SQLAlchemy connector to pull data
from BigQuery? I’m also running Superset on GKE and would appreciate any
insights.
Additionally, if I specify Gunicorn parameters like this in my values.yaml
instead of the way you proposed, would it work the same way?
GUNICORN_TIMEOUT: 300
# Increasing the Gunicorn worker count can drastically improve performance.
# See: https://docs.gunicorn.org/en/stable/design.html#how-many-workers
SERVER_WORKER_AMOUNT: 12
WORKER_MAX_REQUESTS: 1000
WORKER_MAX_REQUESTS_JITTER: 50
SERVER_WORKER_CLASS: gthread
SERVER_THREADS_AMOUNT: 20
GUNICORN_KEEPALIVE: 120
Thanks in advance!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
