You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This slows down the performance of my application, I have used reducer to only get the stores needed and I did try filter to only use the required migrations. Both have made no difference.
I then used filter: (mutation) => console.log(mutation.type) to check what mutations were being called a lot and what might be affecting performance. However, this seems to have fixed the issue. Is there anything I can do to improve performance because consoling out the mutation isn't really a long term solution?
The text was updated successfully, but these errors were encountered:
@jimbrew the reason why your performance is getting better after using filter: (mutation) => console.log(mutation.type) is that this function is supposed to return true for mutations to persist and false for mutations to ignore.
console.log(...) evaluates to false so you are logging all the mutations but filtering them all out. None of them being persisted by vuex-persist.
What helped us with performance is adding the specific module we want to persist
// only persist userState module
modules: ['userState'],
However it is strange how slow it gets. For a 15k loc store (in local storage as json) it is taking almost 2 seconds to commit.
This slows down the performance of my application, I have used reducer to only get the stores needed and I did try filter to only use the required migrations. Both have made no difference.
I then used
filter: (mutation) => console.log(mutation.type)
to check what mutations were being called a lot and what might be affecting performance. However, this seems to have fixed the issue. Is there anything I can do to improve performance because consoling out the mutation isn't really a long term solution?The text was updated successfully, but these errors were encountered: