CODEWITHSUNDEEP
react-nativemobxmobx-react
Ryan Knell
Ryan Knell

Reputation: 6322

Mobx Autorun running too often / need it to skip in some cases / run only after finished

I know its not best practice but its the most performant solution I have found so far. It monitors an object, and transforms that object in the autorun.

This setup is working excellently for small data sets, but when there are a lot of changes, it gets stuck in the "100 cycles and didn't settle" error.

I was wondering if there was some way to get it to iterate just once / collate all changes and apply them in one hit.

I have tried a number of solutions / workarounds that involve timers, deep object comparison (ie don't run if it hasn't changed) etc, but they either disable the autorun or lead to extremely bad performance.

I guess in summary:

Upvotes: 1

Views: 955

Answers (1)

mweststrate
mweststrate

Reputation: 4978

It is hard to say anything useful without some minimal code example of what you are doing. But it sounds like you are reading and modifying the same data in the autorun, which introduces cycles. Consider using reaction which allows you to better separate what data you want to listen react, versus the action you want to take once a change occurs

Upvotes: 2

Related Questions