Has anyone tested measurable performance differences between client-side and server-side Arcade expressions, especially those using geometry functions or multiple feature lookups? Looking for guidance on expression optimization for Web Maps and Experience Builder apps
I’ve been comparing client-side and server-side Arcade behavior in my own dashboards, and performance really depends on how heavy the expression is. Geometry calculations and multiple feature lookups tend to run smoother server-side, especially when layers are large. Client-side logic still works well for lightweight, UI-driven expressions. Clear guidelines would definitely help when deciding where each expression should be executed.