v1.list_pod_for_all_namespaces(watch=False) takes too long

[zzmg]

What happened (please include outputs or screenshots):

In our cluster, there are about 900 pods in total。use v1.list_pod_for_all_namespaces(watch=False)，takes about three seconds，use api_instance.list_deployment_for_all_namespaces，takes about one seconds。in cluser，use kubectl get pods --all-namespaces，takes about one seconds

What you expected to happen:
Can the list pod interface be optimized ？？？
How to reproduce it (as minimally and precisely as possible):
in your cluser，try it
Anything else we need to know?:
no more
Environment:

• Kubernetes version (kubectl version):
  v1.10.5
• OS (e.g., MacOS 10.13.6):
  ubuntu18.04
• Python version (python --version)
  3.6
• Python client version (pip list | grep kubernetes)
  kubernetes 11.0.0

[roycaihw]

I think the main difference is the encoding. The python client uses json and kubectl uses protobuf. Ref #166

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.