Database Architectures & Performance II
As described in the prior post, the shared-disk performance dilemma is simple: 1. If each node stores/processes data in memory, versus disk, it is much faster. 2. Each node must expose the most recent data to the other nodes, so those other nodes are not using old data. In other words, #1 above says flush data to disk VERY INFREQUENTLY for better performance, while #2 says flush everything to disk
Database Architectures & Performance
For decades the debate between shared-disk and shared-nothing databases has raged. The shared-disk camp points to the laundry list of functional benefits such as improved data consistency, high-availability, scalability and elimination of partitioning/replication/promotion. The shared-nothing camp shoots back with superior performance and reduced costs. Both sides have a point. First, let’s look a
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
