Publication
IEEE Transactions on Knowledge and Data Engineering
Paper

Performance Analysis of Affinity Clustering on Transaction Processing Coupling Architecture

View publication

Abstract

Coupling multiple computing nodes for transaction processing has become increasingly attractive for reasons of capacity, cost, and availability. This paper presents a comparison of robustness (in terms of performance) of three different architectures for transaction processing. In the shared nothing (SN) architecture, neither disks nor memories are shared. In the shared disk (SD) architecture, all disks are accessible from all nodes, whereas in the shared intermediate memory (SIM) architecture, a shared intermediate level of memory is introduced. Coupling multiple nodes inevitably introduces certain interferences and overheads, which take on different forms and magnitudes under the different architectures. Affinity clustering, which attempts to partition the transactions into affinity clusters according to their database reference patterns, can be employed to reduce the coupling degradation under the different architectures, though in different ways. However, the workload may not be partitionable into N affinity clusters of equal size, where N is the number of nodes in the coupled system, so that the load can be evenly spread over all nodes. In addition to balancing the load, we need to maintain a large fraction of data references within the database affiliated with the affinity cluster. These become increasingly harder to achieve for large values of N. In this paper, we examine the impact of affinity on the performance of these three different coupling architectures. Our modeling approach is analytical, employing various existing submodels for buffer, concurrency control, and system resources that have been validated extensively in earlier works. The emphasis here is not to develop a new methodology, but to understand the robustness of each of the architectures over a wide range of workload and system parameters, and to identify the workload characteristics best suited for each architecture. © 1994 IEEE

Date

Publication

IEEE Transactions on Knowledge and Data Engineering

Authors

Topics

Share