hyperfiddle

2025-05-16T15:18:14.280419Z

I’m porting my app from Electric v2 to v3, and I have several places where things are noticeably slower with v3. These are all places where my app changes many DOM elements or removes many DOM elements. Adding elements seems less of an issue. Partly this is app functionality, but I also have it in dev when I save a file and the browser gets ready for me to interact with it again. (Not sure what’s going on internally here, but perhaps DOM elements are being modified, or maybe unloaded and reloaded.) I’m wondering whether this is a known issue and whether there might be improvements in the pipeline. If there are no plans to improve things, I will probably have to re-think some aspects of my app. FWIW, I have DOM elements numbering in the low thousands — not sure if that’s something Hyperfiddle are interested in supporting.

Dustin Getz (Hyperfiddle) 2025-05-16T15:48:06.558109Z

there's a long known perf issue in e/for that we're working on next i think

Dustin Getz (Hyperfiddle) 2025-05-16T15:48:39.778319Z

yes, improvements are coming

2025-05-16T15:49:30.607289Z

Ok; thanks. Good to know.