Panel: The Dashboard That Grew - A Scaling Saga
summary
Claims a migration from Streamlit to Panel to handle scale and shows the concrete numbers: 100 to 2000+ users in less than 2 months. Describes running on Kubernetes, hits performance pain: cascading filter logic, data growth forcing caching, tabs causing full-graph renders, and a critical bug where state is shared across sessions because of how apps are served via Bokeh/websockets. Explains fixes tried, tradeoffs between Python-first UI vs separating an API/backend, and which choices actually worked.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:08What is the dashboard and why it grew too much
- 4:41Streamlit’s strengths and limits
- 7:52Panel introduction
- 10:21Panel features deep dive
- 13:56Filter cascading issues
- 16:43Data loop trade-offs
- 20:37Shared state incident
- 22:01Tabs performance pitfalls
- 24:51Testing scaling bottlenecks
- 26:14Key lessons and future
- 27:39Q&A
related talks
50mPanel: Large Scale Streaming in Production
48mPanel
40mHacking the Pachyderm: Scaling Servers and People
46mPanel Discussion: The number of orche
42mThe Challenges Managing a Kubernetes-Based Machine Learning Infrastructure
47mScaling: from 0 to 25 million users
31mKeynote Panel: Node.js at Massive Scale
33mA Monolith, a Microservices, and a Function Walk into a Bar
