You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Curious if there are any established patterns for debugging or profiling leptos applications.
In general I prefer to try and be at least a little proactive about performance before the technical debt build up is too high.
I know of general web/web assembly profiling tools but was wondering if there's anything specific to leptos to track signal usage (counts or breadth of the reactive graph)
Specifically concerned about things like ideal Memo usage (like not incorrectly re-rendering a large list by misusing ) or just measuring if there's a noticable difference between using Memo everywhere vs closures or derived signals (I know this is a bit vague but like where's the cutoff, and how would you know until you have thousands of them)
Also memory use - there can be a lot of gets/reads/collects that go on, and wondering how one might narrow down where to look if profile comes up with some anomalously high usage.
I'm sure there are also possibilities for more advanced tools similar to react dev tools that highlights borders around dom elements when they're re-rendered or solid dev tools which show the reactive tree, which would also be nice, but a separate discussion
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Curious if there are any established patterns for debugging or profiling leptos applications.
In general I prefer to try and be at least a little proactive about performance before the technical debt build up is too high.
I know of general web/web assembly profiling tools but was wondering if there's anything specific to leptos to track signal usage (counts or breadth of the reactive graph)
Specifically concerned about things like ideal Memo usage (like not incorrectly re-rendering a large list by misusing ) or just measuring if there's a noticable difference between using Memo everywhere vs closures or derived signals (I know this is a bit vague but like where's the cutoff, and how would you know until you have thousands of them)
Also memory use - there can be a lot of gets/reads/collects that go on, and wondering how one might narrow down where to look if profile comes up with some anomalously high usage.
I'm sure there are also possibilities for more advanced tools similar to react dev tools that highlights borders around dom elements when they're re-rendered or solid dev tools which show the reactive tree, which would also be nice, but a separate discussion
Beta Was this translation helpful? Give feedback.
All reactions