We need to implement a dirty flag because saving the data for all dimensions has the potential to be a heavy operation. That might explain people's suspicions that having a lot of pocket dimensions causes servers to slow down noticeably.
It might also be a good idea to add time constraints to our saving code so that it runs under a time limit. We can have a forced full save at the end when the server shuts down.
We need to implement a dirty flag because saving the data for all dimensions has the potential to be a heavy operation. That might explain people's suspicions that having a lot of pocket dimensions causes servers to slow down noticeably.
It might also be a good idea to add time constraints to our saving code so that it runs under a time limit. We can have a forced full save at the end when the server shuts down.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We need to implement a dirty flag because saving the data for all dimensions has the potential to be a heavy operation. That might explain people's suspicions that having a lot of pocket dimensions causes servers to slow down noticeably.
It might also be a good idea to add time constraints to our saving code so that it runs under a time limit. We can have a forced full save at the end when the server shuts down.