Ipynb Server startup really slow

Jupyterhub is very slow to access ipynb Server.It took me 9 seconds to into ipynb Server.

@choldgraf,can you help me

A quick thought: It could be that your internet connection is slow, this often makes it take a while to load the notebook interfaces. Perhaps you can run the hub in a data center that is closer to where you’re accessing it?

It is Local Area Network.Are there any other reasons?I guess configurable-http-proxy’s the reason. I’m not sure so Please help me analyze it.

I couldn’t upload the video, so I uploaded a picture instead.Waiting too long is not good for the user experience, so I want to improve. I couldn’t find anything on Zero to JupyterHub on Kubernetes.Please help me. God bless you.

A few things you could investigate:

  • If you run jupyter notebook locally do you see the same slowness?
  • Do you have a HTTP proxy, either explicitly set, or transparently implemented by your network provider?
  • Is there a local or network firewall?
  • Do you have any anti-virus or malware scanners on your system that might be slow or badly configured?
  • If you deploy another remote web application instead of JupyterHub is it also slow?
  • Does your JupyterHub have sufficient resources?
  • Is there anything else running on your local system consuming CPU/RAM/network resources?

I’m this topic author.The server is on the local network. The server performance is completely fine. Zero to JupyterHub on Kubernetes has a proxy called configurable-http-proxy’. configurable-http-proxy fully installs values.yaml.

The server is not affected by CPU/RAM/network/anti-virus/malware.So I suspected configurable-http-proxy was wrong with him.But configurable-http-proxy executed according to default configuration values.yaml.It is Zero to JupyterHub on Kubernetes .