The overhead for a simple textarea seems significant. On Firefox there are stalls (up to 500 ms) if I type "fast". I've tested the form on http://redux-form.com/5.2.5/#/examples/simple?_k=8ukhm8 (specifically the textarea).
Here is the CPU time graph during my tests: http://imgur.com/we9uGQ7
EDIT: OK apparently it's not accurate, see comment below.
Confirmed; just tested on my machine (Firefox, i7-3632QM @ 2.2GHz) by mashing on the keyboard. CPU spikes to 100% on one core and results in stalling.
In contrast the React+Redux app I'm working on uses the local Controller/Component state method and mashing on the keyboard there gave ~20% CPU.
I never would have imagined that Redux Form would lag on a desktop/laptop. I was more concerned that mobile performance would suffer. It's kind of impressive that a simple form can lag a desktop browser...
Re:A SoundCloud client in React and Redux
by groovytime on Sunday June 12, 2016 @09:59PM
(#11891324)
He has redux dev tools enabled, hence the performance issues.
Indeed it behaves much better on a demo I found elsewhere, sorry for the inaccurate comment.
For improved performance (especially on big/complex forms) I suggest looking/using v6 (technically still in alpha, but stable).
Re:A SoundCloud client in React and Redux
by davidjnelson on Sunday June 12, 2016 @09:07PM
(#11891146)
While a super cool and important project, it's a ton of work to integrate into an app when you have maybe 3 sets of radio buttons to deal with, such as when doing an incremental migration refactoring.
>it's a ton of work to integrate into an app when you have maybe 3 sets of radio buttons to deal with
Untrue. It easily reduces the amount of code in your component, and actually gives you the ability to make your FormComponent as a stateless component.
https://gist.github.com/sorahn/6fac9f4717a81c96cd97e2bcc86a1...
It basically works as per your first guess: Everything goes in the store. And no, it doesn't really have any performance or efficiency issues. Try it out and see. :)