apex/DimDoors
1
1
Fork 0
Code Issues 26 Pull Requests Actions Packages Projects Releases Wiki Activity

Must Implement Dirty Flag #146

New Issue
Closed
opened 2014-03-26 06:59:39 +00:00 by SenseiKiwi · 0 comments
SenseiKiwi commented 2014-03-26 06:59:39 +00:00 (Migrated from github.com)
Copy Link

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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
duplicate
enhancement
invalid
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
apex
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: apex/DimDoors#146
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?