Performance regression on large tables

[kevin-j-morse]

Problem:

I was playing around with Sortable a few months ago and it was working great for large (~500 rows) tables aside from some strange ghosting issues that only appeared in Chrome on Windows when using Windows built in DPI scaling. The version I was using back then was 1.10.0-rc3

I updated my project to use the latest release of Sortable so I could check if the ghosting issue is still present. Sadly, it is. Additionally there is now a large pause before the tr leaves one tbody and enters into the other tbody.

JSBin/JSFiddle demonstrating the problem:

https://jsbin.com/bisucakeze/1/edit?html,js,output is 1.10.0-rc3 https://jsbin.com/pusiboxaji/1/edit?html,js,output is latest

[kevin-j-morse]

The regression seems to have come between 1.10.0-rc3 and 1.10.0

latest is maybe a little better than 1.10.0 but still not usable

[FynnZW]

I have a similar problem. Setting animation: 0 solves it for now

[DerekJDev]

Is there any update on this?

I was running into performance issues using version 1.14.0 (Latest) when I had are 150 sortable instances. I tried commenting out the events, but still had lots of lagging making my app non-usable. I tried setting all the instances to forceFallback: true and animation: 0, but that still didn't help.

To fix this the only thing that I found to work was reverting back to version 1.9.0.

[DerekJDev]

I believe the issues #1418 #1108 #1109 all are related to this issue.

[kamikaze942]

Any update on this? this is major blocking issue for my project. and digging through suggested solutions hasn't yielded anything yet. not sure if this code is maintained anymore...