Differences between Oracle DRCP and PHP

The following articles mainly introduce how Oracle DRCP correctly solves the following two problems. Its shared connections can span Apache and middleware nodes, however, the shared connections are based on the relevant database users. For example, all the connections that Scott users log on to the database are shared.

Oracle's support for PHP has always been good (it seems that there are not many PHP + Oracle development projects in China ). The new feature Database Resident Connection Pool (Oracle DRCP) in Oracle 11g makes it possible to further expand the PHP application.

This feature should focus on PHP applications. PHP does not support true multithreading. non-persistent connections consume CPU resources and have poor scalability. Persistent connections have better scalability, but it also occupies more memory resources (the father of PHP explained the impact of connection overhead on the application in a Step-by-Step optimization demonstration article a few years ago ).

The emergence of Oracle DRCP can better alleviate the above two problems. Its shared connections can span Apache and middleware nodes, but the shared connections are based on database users, for example, the Scott user logs on to the database and shares all connections.

According to the test data officially disclosed by Oracle, on a 4-CPU Intel Xeon MP 2.80 GHz machine, 2 gb ram, 32bit RHEL 4. when 14000 connections are supported, the CPU usage is around 65%. This is amazing. According to another test result I found, it seems that it is necessary to make a big discount to provide reference.

Article by: http://database.51cto.com/art/200703/43583.htm