On 11/02/2013 08:18, Nitai @ Razuna wrote:
This is nice. Would you mean explaining about the Database
enhancements? Especially, "DataSourceActivePoolStats" and
"connectionperpage" and how it would affect.
The 'DataSourceActivePoolStats()' is a function that will display all
the stats for all your database connection pools, the numbers of hits,
timeouts etc. Rich array of data in there.
Now, the "connectionperpage" is a new feature that we wouldn't recommend
for every environment. What this one does, is that for every page
request, when you need a connection to the database, it will create one
there and then, and only cache it for the duration of the page, after
the request ends, the connection is closed. This disables the overall
pool system. Seems wrong doesn't it? Goes against years of
conventional thinking with respect to pooling.
However ... this has been added for a couple of reasons - take advantage
of the new high performance connection pooling of MariaDB that is
designed to handle 200,000+ concurrent connections as well as for
environments, where you database may be moving around a lot (for example
in a cloud environment, where it will pop up on a new IP addresss (dns
ttl turned right down to seconds)).
In our tests, it is only adding a few milliseconds to each page that has
to establish a connection.
By default this feature is off. But DataSourceCreate()/xml supports it
(use <connectionperpage>true</connectionperpage> inside the datasource
xml block).
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
