Terrible performance in Chrome and IE

[francispelland]

I am running into some intense performance issues. I wasn't running into this during initial development, however when I rolled out my tools into prod I started running into these issues.

Per form, I am displaying 9 input fields. 3 of those input fields use selectize. While developing, I was running no more than 5 forms per page. However now that I launched on prod, I have over 50 forms, since each form is a customer. Though I intend to add pagination, I am expecting to always have 50 per page.

I've updated my code so that I only load selectize on the currently visible form. The execution time is now around 1-2 seconds rather than 75 seconds. This is tested on the latest version of Chrome, IE 10, and IE 11. This does not happen in IE9.

Using IE's profiler, I was able to drill down into the call stack to notice the slowest method call was "offsetWidth".

Here is the stack for a bit more information:

[cvillemure]

We also have this issue, typing in the input box is lagging big times in IE9 and IE10.

We've overwritten the autoGrow function until a fix is provided

[jasonshaev]

Having similar performance issues with many selectize plugins on the same page. @cvillemure curious what your solution was? I'd think this resize should be debounced at least.

[whather]

I'm also getting horrible performance with autoGrow in Chrome (super choppy performance when typing). @cvillemure it would make my day if you shared your autoGrow implementation.

Cheers!

[whather]

I decided to re-implement the autoGrow myself using this implementation: https://github.com/MartinF/jQuery.Autosize.Input

whather@4451526

[apneadiving]

I guess its due to measureString https://github.com/brianreavis/selectize.js/blob/master/dist/js/selectize.js#L353 which creates then removes a dom element _every single time_.
The input could be added to the dom to be cached and removed when selectize is removed.

[mikemaccana]

Perf is slow and could be improved, but -1 for the 'perf is terrible'. Rude.

[rubinred]

Please fix this issue, as performance is very poor right now.

[marcotisi]

I've just created a new PR (#1197) which add a plugin called "better_auto_grow".
This plugin should improve measureString performances by appending a "<test>" element only once to body and use it to measure string width.

[marcotisi]

Removed old PR (#1197) and created a new one (#1199) which integrates changes directly into the core.

[marcotisi]

Any news about merging this pull request?

[marcotisi]

Still no news on this?

[risadams]

closing stale issues older than one year.
If this issue was closed in error please message the maintainers.
All issues must include a proper title, description, and examples.

[TyphousCrane654]

I have a list with about 2700 options and confirm that the performance in Chrome is still very poor. In Firefox it's working well.