Project:
| View Revisions: Issue #49631 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0049631: Persist state in LocalStorage instead of in IndexedDB | ||
| Revision | 2022-06-24 09:58 by AugustoMauch | ||
| Description | Persisting the state in IndexedDB has two main disadvantages: - Reading/writing the state will have an impact on other business logic queries because no two IndexedDB operations can be done at the same time - We suspect that the many amount of state read/write operations in IndexedDB is resulting in performance degradation in other databases (i.e. masterdata) We will test how the state is persisted in LocalStorage. This option also has disadvantages, i.e. the state needs to be serialized before being stored. Also we are throttling the state persistence every 10 ms. We should increase that value at least to 100 ms to prevent persisting the state too often. |
||
| Revision | 2022-06-24 09:57 by AugustoMauch | ||
| Description | Persisting the state in IndexedDB has two main disadvantages: - Reading/writing the state will have an impact on other business logic queries because no two IndexedDB operations can be done at the same time - We suspect that the many amount of state read/write operations in IndexedDB is resulting in performance degradation in other databases (i.e. masterdata) We will test how the state is persisted in LocalStorage. This option also has disadvantages, i.e. the state needs to be serialized before being stored. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |