-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance Issue with DnD and onSelectEvent #1103
Comments
We may have addressed this partly in a recent PR, can you try and use the current master and see if it still occurs? If so there could definately be some performance low hanging fruit to be picked, we switched from react-dnd which is pretty tuned and optimized (but not a great solution for us) to something more custom so we haven't had a chance to stress test it in lots of different places. More than happy to take PR's on this front as well if you're up for it |
Hello jquense, I'll look if I found something! |
Commenting these two lines from |
Might be fixed by #1118 |
Thanks, i'll check when your PR is merged |
There are still a bunch of setState calls in there, can you see where they are originating from? |
Possibly this is the same issue I was having. |
Actually, I do not have performance issues with DnD now. Thanks for great fix, bs85! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Do you want to request a feature or report a bug?
Performance issue
What's the current behavior?
Hi there.
I've just updated from 0.19.2 to 0.20.2 and I have a performance issue when using
onSelectEvent
with DnD activatedNo problem with 0.19.2 (i'm using the same code) or if set event
draggable
to false.So I assume there is a leak when detecting
click
event vsstartDrag
/endDrag
I've launched DnD example and added an
onSelectEvent
with aconsole.log
, and I have 1.5s delay before theconsole.log
is triggered, so I assume it's not from my code :)Thanks !
The text was updated successfully, but these errors were encountered: