The Supreme Court curbed the Environmental Protection Agency’s ability to broadly regulate carbon emissions from existing power plants, a major defeat for the Biden administration's attempts to slash emissions at a moment when scientists are sounding alarms about the accelerating pace of global warming.
I appreciate the suggestion. I think that's something that's been discussed before. while I'm not as much of a front-end dev, I've been told that the site's usage of websockets makes this not as bad? don't want to out any of the other devs, but maybe someone else can chime in if they feel comfortable doing so.
Can confirm. The bottlenecks that happen when the site gets high traffic are in the database. New websocket messages happen in response to post and comment creation, which are relatively lightweight operations with a small payload.
So live updates have consistently been an issue that needs to be resolved on the frontend, but making that fix would not stop the site from getting overloaded
Hey, just wanted to ask who the right people to contact are regarding getting a better understanding of the various service interactions and deployment-related stuff for the site.
I'm on the analytics side of database operations (so a slightly difference space than the needs of an API interacting with the DB layer- but still familiar with Postgres which I assume is what is being used since this is a lemmy fork), but I'd still like to get an understanding of how the site's services interact to see if I can potentially find any performance gains that might alleviate some of this stress a bit.
Edit- nevermind. Found resources on the pinned c/technology thread and am looking into them now.
I appreciate the suggestion. I think that's something that's been discussed before. while I'm not as much of a front-end dev, I've been told that the site's usage of websockets makes this not as bad? don't want to out any of the other devs, but maybe someone else can chime in if they feel comfortable doing so.
Can confirm. The bottlenecks that happen when the site gets high traffic are in the database. New websocket messages happen in response to post and comment creation, which are relatively lightweight operations with a small payload.
So live updates have consistently been an issue that needs to be resolved on the frontend, but making that fix would not stop the site from getting overloaded
Hey, just wanted to ask who the right people to contact are regarding getting a better understanding of the various service interactions and deployment-related stuff for the site.
I'm on the analytics side of database operations (so a slightly difference space than the needs of an API interacting with the DB layer- but still familiar with Postgres which I assume is what is being used since this is a lemmy fork), but I'd still like to get an understanding of how the site's services interact to see if I can potentially find any performance gains that might alleviate some of this stress a bit.
Edit- nevermind. Found resources on the pinned c/technology thread and am looking into them now.