Julien Bayle

I'd like to know more about performance comparison between:

- 1 JS parsing A LOT of data coming from 8 sources

- 8 JS parsing data coming from 1 source each one

I'd like to know more about performance comparison between:
- 1 JS parsing A LOT of data coming from 8 sources
VS
- 8 JS parsing data coming from 1 source each one

1-js-parsing-8-data-sources-vs-8-js-parsing-each-1-data-source-which-one-win

What sort of data and what sort of processing? I don't know enough about how javascript works inside of Max to comment on which way would be better. However, if you write your code to do one of the options it shouldn't be a massive headache to modify it to support the other option. You could even run some tests yourself to see which one works best.

those are "just" multisliders lists popping out into JS.

BUT, and it is the important & critical stuff, JS pops out midi note messages to the midiout

actually, it works well (accuracy measured is ok)

I could use a patch instead of the JS ... BUT I need some dynamic array size (which would drive into dynamic patching, possible but not wanted)

Probably, I would "translate" the JS into a C external in order to speed things more

those are "just" multisliders lists popping out into JS.
BUT, and it is the important & critical stuff, JS pops out midi note messages to the midiout 

actually, it works well (accuracy measured is ok)
but I'm not sure about that way.
I could use a patch instead of the JS ... BUT I need some dynamic array size (which would drive into dynamic patching, possible but not wanted)
Probably, I would "translate" the JS into a C external in order to speed things more


1 JS parsing 8 data sources VS 8 JS parsing each 1 data source... which one win?