SL21W41: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 15: | Line 15: | ||
***'''Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched, async, streamed inserts?''' | ***'''Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched, async, streamed inserts?''' | ||
****'''Specifically the data compression would be handy here for non-confirmant itemstacks where all data needs to be logged and not just a LibId''' | ****'''Specifically the data compression would be handy here for non-confirmant itemstacks where all data needs to be logged and not just a LibId''' | ||
****'''"Small datasets typically see no performance advantage on TimescaleDB vs PostgreSQL (in fact, they might be slightly slower)"''' | |||
****'''"The queries run (they should typically be time-oriented restriction clause)"''' |
Revision as of 14:27, 16 October 2021
- Cleanup Week 2
- Completely remove Desktop-special case as a screen, use dynamically created ScreenModel internally to reduce complexity
- Got rid of most of the special caching / update flags for desktop this way
- Code reduction as the general purpose cache now works nicely
- Add a quick board comparison/equality check by comparing screen-size first (+ tile element count second)? Needed? The BoardHash should do this already right?
- Completely remove Desktop-special case as a screen, use dynamically created ScreenModel internally to reduce complexity
- Nils intro to Kadi / Chunkli design
- General setup of Stasi-Plugin, based on Chunkli Api
- Think/Test persistence layer
- Make sure we respect shulker boxes in some way?
- 95% of data is archival data mostly? Important is mostly just worldchanges ~7 days + chat ~3 month; rest can be slow / compressed?
- Most likely PostgreSQL + time-series => Timescale db? on an external logging server with batched, async, streamed inserts?
- Specifically the data compression would be handy here for non-confirmant itemstacks where all data needs to be logged and not just a LibId
- "Small datasets typically see no performance advantage on TimescaleDB vs PostgreSQL (in fact, they might be slightly slower)"
- "The queries run (they should typically be time-oriented restriction clause)"
- General setup of Stasi-Plugin, based on Chunkli Api