AW: [PHP-DB] Limit number of persistent oci8-connections?

MaxClients in httpd.conf reduces your total server performance in case you have not only db-actions but also images and plain files ... if you use something other than ocilogon you open a persistant link that might not be closed. (try using ocilogon instead of eg ociplogon) close every connection with ocilogoff If you are running heavy traffic try to configure your NET8 Listener to work as MTS. This does not create and destroy a process every time you query the server, but delivers all incoming queries to some worlking-server-processes, starting and stopping them when needed, just like apache handles its childs. Increase the Global System Area by incresing the Shared Pool Size of your DB : this will inspire the db to consume more caching ram. On the other site check the ram consumption of oracle... maybe it swaps! If you want to limit your PHP-Scripts connections there is the problem with the synchronisation of the counter: sessions, a file, shared memory/IPC System V. It all doesn't sound very satisfing. Maybe you can place your db-phpscripts into a virtual host or another apache and configure that with a lower maxCLients directive, but this will simply lock out your visitors not giving you a chance to intercept the error message. Another Idea: can you limit the number of concurrent sessions created by one DB-User ? if possible you could assign your scripts a special user and therefore allowing connections with higher priority from e.g. your admin account > On Thu, Jan 25, 2001 at 08:22:07PM +0100, Matthias Kopolt wrote: > > Are you useing persistent connections (I had no real luck > with them)? > > > > How do you connect to your DB over Multi Threaded Server > (MTS) or Dedicated > > Server ? > > I am just using phplib for the dirty stuff :) So I don't know > exactly how > this works under the hood.. > > > I think Oracles NET8 Config has a Parameter to limit this. > > Check out the MasterIndex at > > Well it is limited to 200 connections right now, but I would > like to limit > that on the PHP side rather than on the Oracle side. Although I don't > exactly know why. It just seems right :)