diff --git a/docs/docs/databases/bigquery.mdx b/docs/docs/databases/bigquery.mdx
index 7ea993ae5d4..e42aa46bfb5 100644
--- a/docs/docs/databases/bigquery.mdx
+++ b/docs/docs/databases/bigquery.mdx
@@ -87,3 +87,6 @@ You should then be able to connect to your BigQuery datasets.
 
 To be able to upload CSV or Excel files to BigQuery in Superset, you'll need to also add the
 [pandas_gbq](https://github.com/pydata/pandas-gbq) library.
+
+Currently, Google BigQuery python sdk is not compatible with `gevent`, due to some dynamic monkeypatching on python core library by `gevent`.
+So, when you deploy Superset with `gunicorn` server, you have to use worker type except `gevent`.
diff --git a/docs/docs/installation/configuring-superset.mdx b/docs/docs/installation/configuring-superset.mdx
index 66022521bf6..bfa1b912916 100644
--- a/docs/docs/installation/configuring-superset.mdx
+++ b/docs/docs/installation/configuring-superset.mdx
@@ -146,6 +146,9 @@ for production use._
 If you're not using Gunicorn, you may want to disable the use of `flask-compress` by setting
 `COMPRESS_REGISTER = False` in your `superset_config.py`.
 
+Currently, Google BigQuery python sdk is not compatible with `gevent`, due to some dynamic monkeypatching on python core library by `gevent`.
+So, when you use `BigQuery` datasource on Superset, you have to use `gunicorn` worker type except `gevent`.
+
 ### Configuration Behind a Load Balancer
 
 If you are running superset behind a load balancer or reverse proxy (e.g. NGINX or ELB on AWS), you