github/sql-server-samples
1
0
Fork 0
mirror of https://github.com/Microsoft/sql-server-samples.git synced 2025-12-08 14:58:54 +00:00
Code Issues Releases Wiki Activity

updated formatting

Browse Source
This commit is contained in:
Jos de Bruijn
2017-12-20 13:56:24 -08:00
committed by GitHub
parent 7278971bc4
commit dc0494caaf
1 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
samples/features/in-memory/ticket-reservations/README.md
+9 -8
View File
@@ -50,14 +50,15 @@ The demo is run in this [17-minute video explaining In-Memory OLTP](https://www.
11. Go back to the app and run the workload again. No need to recompile or restart the application.
The perf gains from In-Memory OLTP as shown by the load generation app depend on two factors:
- Hardware
- more cores => higher perf gain
- slower log IO => lower perf gain
- Configuration settings in the load generator
- more rows per transaction => higher perf gain
- more reads per write => lower perf gain
- default setting is 100 rows per transaction and 1 read per write
The perf gains from In-Memory OLTP as shown by the load generation app depend on two factors:\
- Hardware
- more cores => higher perf gain
- slower log IO => lower perf gain
- Configuration settings in the load generator
- more rows per transaction => higher perf gain
- more reads per write => lower perf gain
- default setting is 100 rows per transaction and 1 read per write
If the performance profile after migration to In-Memory OLTP looks choppy, it is likely that log IO is the bottleneck. This can be mitigated by using [delayed durability] (https://msdn.microsoft.com/en-us/library/dn449490.aspx). This is enabled by running the following statement in the database:
`ALTER DATABASE CURRENT SET DELAYED_DURABILITY = FORCED`