Dedicated Server Configuration (133)
The user and server processes are separate, distinct processes. The separate server
process created on behalf of each user process is called a dedicated server process (or
shadow process), because this server process acts only on behalf of the associated user
process.
This configuration maintains a one-to-one ratio between the number of user processes
and server processes. Even when the user is not actively making a database request,
the dedicated server process remains (though it is inactive and can be paged out on
some operating systems).
In the dedicated server configuration, the user and server processes communicate
using different mechanisms:
■ If the system is configured so that the user process and the dedicated server
process run on the same computer, the program interface uses the host operating
system’s interprocess communication mechanism to perform its job.
■ If the user process and the dedicated server process run on different computers,
the program interface provides the communication mechanisms (such as the
network software and Oracle Net Services) between the programs.
■ Dedicated server architecture can sometimes result in inefficiency. Consider an
order entry system with dedicated server processes. A customer places an order as
a clerk enters the order into the database. For most of the transaction, the clerk is
talking to the customer while the server process dedicated to the clerk’s user
process remains idle. The server process is not needed during most of the
transaction, and the system is slower for other clerks entering orders. For
applications such as this, the shared server architecture may be preferable.
專有服務
使用者程式和服務程式分隔開 , 服務程式為每個使用者程式建立一個專有連線 , 是1對1的
在專有服務模式下 , 使用者和服務程式透過不同機制連線 :
1. 使用者和服務程式執行在同一機器上 , 程式介面使用作業系統程式間通訊機制
2. 使用者和服務程式執行在不同機器上 , 程式介面在程式見提供通訊連線機制
3. 專有模式下在有些時候是低效的 .
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/10599713/viewspace-980725/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MySQL 8.0 Reference Manual(讀書筆記77節--Merge Threshold for Index Pages & Automatic Configuration for a Dedicated MySQL Server)MySql筆記IndexServer
- [20211012]sqlnet.ora USE_DEDICATED_SERVER=on.txtSQLServer
- web server apache tomcat11-12-SSL/TLS ConfigurationWebServerApacheTomcatTLS
- LeetCode-133-克隆圖LeetCode
- redis configurationRedis
- 2.15 Kamui ——ARC131~133UI
- etcd install & configuration
- openwrt advanced configuration
- 9.(轉)Spring Configuration Check Unmapped Spring configuration files foundSpringAPP
- PostgreSQL DBA(133) - Extension(postgresql_anonymizer)SQL
- .net core Configuration物件物件
- spring 解析 @Configuration 流程Spring
- 133、賦得暮雨送李胄
- Day133.異常處理 -SpringMVCSpringMVC
- JSR - 133 都解決了哪些問題?JS
- 救濟金髮放( The Dole Queue, UVa 133)
- ORA-07445: exception encountered: core dump [qervwRowProcedure()+133]Exception
- .Net Core Configuration原始碼探究原始碼
- Spring處理@Configuration的分析Spring
- new sublime text4 configuration
- SAP Spartacus Multi-Site Configuration
- Spring Boot Configuration Annotation Processor not configuredSpring Boot
- @Configuration, @Bean 註解的作用Bean
- 【Spring 註解】@Configuration和@BeanSpringBean
- iOS開發基礎133-崩潰預防iOS
- JSR133提案-修復Java記憶體模型JSJava記憶體模型
- Spring-@Configuration註解簡析Spring
- 理解ASP.NET Core - 配置(Configuration)ASP.NET
- How to Understand Transportation Lane Configuration in SAP SNP
- asp.net core 系列之ConfigurationASP.NET
- Spring管理的@Configuration註解使用Spring
- Error: Cannot find configuration directory: /etc/hadoopErrorHadoop
- HITSC_3_Software Construction Process and Configuration ManagementStruct
- Spring中@Component和@Configuration的區別Spring
- Springboot中註解@Configuration原始碼分析Spring Boot原始碼
- .Net Core Configuration Etcd資料來源
- MongoDB:Read and write access to data and configuration is unrestricted.MongoDBREST
- Java記憶體模型FAQ(三)JSR133是什麼?Java記憶體模型JS
- 尚觀Linux最佳入門高清視訊教程033/133/253Linux