In-Memory OLTP in Azure SQL Database | Microsoft Azure Blog
Table 1: Performance comparison for a sample order processing workload * For the run on P15 we used a scale factor of 100, with 400 clients; for the P2 run we used scale factor 5, with 200 clients. Scale factor is a measure of database size, where 100 translates to a 15GB database size, when using memory-optimized tables. For details about the workload visit the SQL Server samples GitHub repositor
OLTP Through the Looking Glass, and What We Found There
OLTP Through the Looking Glass, and What We Found There Stavros Harizopoulos HP Labs Palo Alto, CA stavr[email protected] Michael Stonebraker Samuel Madden Daniel J. Abadi Yale University New Haven, CT [email protected] Massachusetts Institute of Technology Cambridge, MA {madden, stonebraker}@csail.mit.edu ABSTRACT Online Transaction Processing (OLTP) databases include a suite of features — disk-resident B-
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}