> > Other approaches to limit load on the db might be reasonably employed - > at > > least for the transition phase: you can limit the nuber of concurrently > > handled web requests. Although that would be a stronger restriction > than > > the one you want, it might be ok for the transition. > > That's not that simple: There is only a web application: Some functions > are > rewritten in Zope, they query the database directly via Zope/Python. Other > functions remain in a C library (which access the database) are called > from > Zope/Python. Both connections should be handled together as they both are > integrated in one web application.
Apparently I was not clear enough: limiting the number of concurrent active requests would be done in the webserver via some config setting. And if only at most n web requests can be concurrently running there will be no more than n concurrent db connections - unless a single request spawns new threads or processes that connect to the db of course. Kind regards robert -- +++ GMX DSL Premiumtarife 3 Monate gratis* + WLAN-Router 0,- EUR* +++ Clevere DSL-Nutzer wechseln jetzt zu GMX: http://www.gmx.net/de/go/dsl -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
