Any Performance related improvement while running JSXBIN as compare to JSX

One could write a book on JSX performance optimizations, but the major principle is to first measure, then optimize.

E.g. having stray folder aliases within the startup scripts folder causing recursion can result in really bad execution times - especially if your server decides to restart too frequently.

Not that extreme, but it is anyway worth to have a look at all startup scripts including preinstalled ones and reconsider whether you really need to support e.g. hyperlink or footnote related menu items. In. InDesign. Server.

Regarding measurements, if you have not yet seen that, $.hiresTimer can be very useful, e.g. when you need a better granularity than the ESTK profiler (you know of the profiler, do you?) or when the profiler just chokes due to code size (you'll get to that with some hundred thousand lines of code).

Finally, if the load time turns out to be a concern at all, you can load all your methods into a permanent targetengine once at startup rather than with every iteration.

Hi @samy@123,

Why don't you give it a try and let us know, you have things setup already, give it a go and compare the results. In my opinion the chances of it being slower are a bit more, the reason I say is the overhead for converting the encoded code back into a format the JS interpreter understands. It could be faster in case the jsxbin conversion also involves some optimisations done by the encoder. However, in either case I am not hopeful that the difference would even be on noticeable spectrum.

P.S.:- All this is conjecture and you are welcome to share your test results to put some facts on the table.

-Manan