Deletion time #54

Open
jtrimble2100 opened this Issue Sep 19, 2012 · 1 comment

Projects

None yet

2 participants

Deleting user objects from the user environment can take so long that the user things the command has failed.

Member

Should investigate making polling frequency for database plugin configurable (may be the case already). A shorter polling interval (~200ms) should make this unnoticable to user.

@VWoeltjen VWoeltjen added a commit to VWoeltjen/mct that referenced this issue Sep 16, 2013
@VWoeltjen VWoeltjen [Database] Allow configuration of polling interval
Reduces database polling interval, and allows
configuration on a per-user basis. This addresses
both perceived and actual issues with object
modification:

* nasa/mct#54 notes that object deletion seems
  to take a long time. Root cause is that the
  Browse area is refreshed by database polling,
  which takes place at a longer interval (3s).
  Decreasing this interval means that the user
  sees the consequences of their action sooner.
* nasa/mct#132 occurs when the user switches
  back and forth between objects faster than
  the poll interval. This can cause an object
  to be flagged as stale because changes from
  one save have not made their way back to
  the Browse area. While this still may occur
  with a shorter polling interval, the odds
  of the user observing this decrease
  significantly.
* nasa/mct#111 describes latency issues, some
  of which may be related to the poll
  interval. (It is unlikely, however, that
  menu item latency is related to this.)
b57f7b4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment