I'm surprised more projects aren't having this MySQL scaling issue in #PHP.... - PHP

jeff, 4 months ago

I'm surprised more projects aren't having this MySQL scaling issue in #PHP.

MYSQLI_OPT_CONNECT_TIMEOUT only affects the TCP init, not the time to first byte.

MYSQLI_OPT_READ_TIMEOUT is then also needed to time out quickly if a socket connects but sends no data in a reasonable time (DoS otherwise).

However, that also aborts queries that run longer than the limit (reports, schema upgrades).

You have to set the timeouts before a connection and can't use @@session.

https://bugs.php.net/bug.php?id=76703

reply

report

activity

copy /kbin url

copy original url

open original url

Loading...

Image

Image alternative text

ramsey, 4 months ago

@jeff Maybe because more folks use PDO_MYSQL instead of mysqli?

reply

report

activity

copy /kbin url

copy original url

open original url

Loading...

jeff, 4 months ago

@ramsey Sure, that's possible. I'll check if PDO avoids the issue, but a glance at the docs seems like ATTR_TIMEOUT doesn't make a connection / read distinction for MySQL either.

The bug report proposes a reasonable change of including the max-time-to-first-byte in the connection timeout so connect/read are properly decoupled. RDS has had this issue a few times (probably load balancer related).

Cerb is likely older than PDO, so that's not an easy change. I'd break more than I fix. 😅

reply

report

activity

copy /kbin url

copy original url

open original url

Loading...

Add comment