🔗 Django LiveView vs Phoenix LiveView: a real benchmark

How does Django LiveView stack up against Phoenix LiveView in real-world scenarios? In a recent benchmark, identical alert dashboards were built in both frameworks to measure performance under realistic conditions. The tests showed that both frameworks performed similarly, with around 22 ms for mutations and 7 ms for search in most scenarios.

However, the stark differences emerged in payload sizes and scalability. With larger lists, Django LiveView significantly increased its data transfer, sending more bytes per interaction than Phoenix. Conversely, as the number of concurrent users increased, Phoenix exhibited better scaling capabilities. While Django LiveView allows more explicit control over updates, the inherent advantages of Phoenix's design can lead to lower latency under load. Overall, they are comparable, but for heavy payloads and concurrency, Phoenix may have the edge.