News for hackers. Stuff that matters.

A comment on Python stands to lose its GIL, and gain a lot of speed. Parent comment

Re:Python stands to lose its GIL, and gain a lot of speed by rbjorklin on Sunday October 17, 2021 @12:18PM (#28897528)
One thing that comes to mind is for shared connection pools when you have thousands of workers connecting to the same stateful service.
[ Parent | on HN ]
Re:Python stands to lose its GIL, and gain a lot of speed by TekMol on Sunday October 17, 2021 @12:38PM (#28897682)
Which use case requires such a setup?
[ Parent | on HN ]
Re:Python stands to lose its GIL, and gain a lot of speed by Spivak on Sunday October 17, 2021 @01:04PM (#28897889)
MySQL comes to mind. Unlike Postgres where connections are expensive MySQL encourages loading up the server with hundreds of simultaneous connections per server.

Like anything, it’s possible to split this work out to a separate process but the IPC overhead is a lot.

[ Parent | on HN ]
Re:Python stands to lose its GIL, and gain a lot of speed by lazide on Sunday October 17, 2021 @12:42PM (#28897717)
Most databases (unfortunately), and since a ton of web apps use databases for state..

That said, many such databases are (or already have) rolled out connection pool proxies for reasons like this, so meh.

[ Parent | on HN ]
Re:Python stands to lose its GIL, and gain a lot of speed by lanstin on Sunday October 17, 2021 @12:47PM (#28897756)
Web front end backed by data base with expensive login, so you cache connections. Two tier architecture it would be called.
[ Parent | on HN ]