DorkasV / jira-to-github-issues

0 stars 0 forks source link

Analyse af implementering af Memory-Optimized Tables #87

Open sync-by-unito[bot] opened 6 months ago

sync-by-unito[bot] commented 6 months ago

For at kunne give JAR db et performance boost, så kan vi overveje at tage Memory-Optimized Tables i brug. Dette kunne f.eks. være på e_gis.

https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/overview-and-usage-scenarios?view=sql-server-ver15 Use memory-optimized tables for your core transaction tables, i.e., the tables with the most performance-critical transactions. Use natively compiled stored procedures to optimize execution of the logic associated with the business transaction. The more of the logic you can push down into stored procedures in the database, the more benefit you see from In-Memory OLTP.

To get started in an existing application:

Use the transaction performance analysis report to identify the objects you want to migrate. https://docs.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/determining-if-a-table-or-stored-procedure-should-be-ported-to-in-memory-oltp?view=sql-server-ver15

Use the memory-optimization and native compilation advisors to help with migration.

Der ønskes en analyse af fordele og ulemper ved at anvendes Memory-Optimized Tables på JAR db, herunder konkrete forslag til hvilke tabeller hvor dette kunne anvendes med fordel.

┆Attachments: image-20220107-101240.png | image-20220107-101308.png | MigrationAdvisorChecklistReport_e_gis_20220107.html

sync-by-unito[bot] commented 6 months ago

➤ Peter Riis commented:

!image-20220107-101240.png|width=705,height=505!

!image-20220107-101308.png|width=699,height=504!

sync-by-unito[bot] commented 6 months ago

➤ Peter Riis commented:

Hvis der ønskes en optimering af e_gis, så kunne en mulighed være at partitionere e_gis i 2 - en del med de aktive kortlægningsgeometrier (som oftes anvendes) og alle andre.

De aktive kortlægningsgeometrier er dem hvor e_gis.gis_ref_nr = e_forurening_version.flade_id.

Det kræver muligvis en ny kollone i e_gis (bit) om geometrien opfylder e_gis.gis_ref_nr = e_forurening_version.flade_id eller ej.

https://docs.microsoft.com/en-us/sql/relational-databases/partitions/partitioned-tables-and-indexes?view=sql-server-ver15 ( https://docs.microsoft.com/en-us/sql/relational-databases/partitions/partitioned-tables-and-indexes?view=sql-server-ver15|smart-link )