• 3 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • It’s the ActivityPub API (client to server) where clients supposed to interface with so that you could have one client, for all fedi. But turns out server implementations (Lemmy, mastodon etc) find it not so well designed or performant or adequate (or idk what else) so instead they implement their own client APIs, effectively making clients being specific to the server rather than interoperable (one client that could understand all servers). It’s reasonable though, it’s just … I thought… that this was already done and established… but well…













  • At a first level it certainly is an issue with PHP, but PHP was also designed by a human. That design comes with its own problems right? I guess what I said is just a generalisation of PEBKAC as all (mostly all) software is designed by some human. Fact that it’s a different chair may as well be considered not a PEBKAC ? Yes it’s philosophical or simply which perspective you choose to see.

    Haven’t played with amphp/parallel but maybe worth a look to see how/if sockets are shared there.








  • Also how’s the setup? You setup for example 5 max children in fpm and 5 persistent connections? Per server? So your overall connections to the db server will be 5x your server instances?

    If you setup 5 fpm children and less connections, one child will eventually reuse from another, but only when the connection is free (does not do a query for another process or pdo does not consume a resultset). If it tries to do a query at that time it will have to wait and it will block. This is my understanding. Also how you do transactions with persistent connections?

    This has evolved into such an interesting conversation.