[wp-trac] [WordPress Trac] #31018: Persistent database connections with mysqli

[WordPress Trac]

#31018: Persistent database connections with mysqli
-------------------------------------+------------------------------
 Reporter:  blobaugh                 |       Owner:
     Type:  enhancement              |      Status:  reopened
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Database                 |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+------------------------------
Description changed by SergeyBiryukov:

Old description:

> WordPress currently does not allow support for persistent database
> connections. This can be accomplished by prepending "p:" to the hostname
> with mysqli however with its current configuration WordPress will be
> confused by the ":" and think the hostname is actually a port if
> specified in the wp-config.php file. This patch add support for a
> constant that allows persistent connections to be turned on or off.
>
> Why should this be added to core? Because persistent connections are
> useful :P. But really, we have seen requests for this in other tickets
> such as https://core.trac.wordpress.org/ticket/27933. Additionally I am
> involved in a project where 10,000+ sites are requiring persistent db
> connection, not an insignificant number. Persistent db connections are
> also needed to ensure proper performance on IIS and Azure installations.
>
> In short a couple lines of code is all it takes to ensure WordPress
> continues to work well across other platforms and project requirements.
>
> Props to awoods and bradparbs for helping identify the issue and
> solution.

New description:

 WordPress currently does not allow support for persistent database
 connections. This can be accomplished by prepending "p:" to the hostname
 with mysqli however with its current configuration WordPress will be
 confused by the ":" and think the hostname is actually a port if specified
 in the wp-config.php file. This patch add support for a constant that
 allows persistent connections to be turned on or off.

 Why should this be added to core? Because persistent connections are
 useful :P. But really, we have seen requests for this in other tickets
 such as #27933. Additionally I am involved in a project where 10,000+
 sites are requiring persistent db connection, not an insignificant number.
 Persistent db connections are also needed to ensure proper performance on
 IIS and Azure installations.

 In short a couple lines of code is all it takes to ensure WordPress
 continues to work well across other platforms and project requirements.

 Props to awoods and bradparbs for helping identify the issue and solution.

--

--
Ticket URL: <https://core.trac.wordpress.org/ticket/31018#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform