TP Monitor Architectures (Cont.) Process per client model-instead of individual login session per terminal,server process communicates with the terminal,handles authentication,and executes actions. Memory requirements are high Multitasking-high CPU overhead for context switching between processes Single process model-all remote terminals connect to a single server process. Used in client-server environments Server process is multi-threaded;low cost for thread switching No protection between applications Not suited for parallel or distributed databases Database System Concepts,5th Ed. 25.4 ©Silberschat乜，Korth and SudarshanDatabase System Concepts, 5 25.4 ©Silberschatz, Korth and Sudarshan th Ed. TP Monitor Architectures (Cont.) Process per client model - instead of individual login session per terminal, server process communicates with the terminal, handles authentication, and executes actions. Memory requirements are high Multitasking- high CPU overhead for context switching between processes Single process model - all remote terminals connect to a single server process. Used in client-server environments Server process is multi-threaded; low cost for thread switching No protection between applications Not suited for parallel or distributed databases