preset manager limitations

[tester]

I'm starting to wonder where is the borderline of performance for preset manager.

Just did a little test with preset params to common string conversion and here are some thoughts.

at 2400 parameters to store: 40 seconds loading time
at 1400 parameters to store: 10 seconds loading time
sound offline.

*

Under test:

1) It is better to do more smaller "preset string" modules than less and larger ones. I mean it. When preset string deals with 40-80 switches, then arrays update start to play signifficant role. I suspect a good thing is around 10 switches per array->string. Then you can resign from manual retriggering for "store and load preset values"; just need to use "changed" to limit amount of updates (array, value reload).

2) It's good to use "preset string" routine/conversion only for static values and switches only. They change only on user interaction, and it means - the array change, not only the single value.

Now it's time to push inside some streamy guts to add blue load on preset routines.

//edit: works under load too.

Ehm.... in a few days back to the old project again