What an adorable kangaroo
GentriFriedRice
joined 1 year ago
Maslow's hierarchy of R I C E
Most modern websites are multiple servers with servers being a specialized computer with no screen that has all the software needed to run the website. Each of these individual computers can each show you the website but it's somewhat random as to which you will connect to when you connect with your web browser (i.e, a request). Having multiple computers able to show you the website is one way software like lemmy is designed to help reduce its load -- often termed load balancing.
To make your website be able to be split between multiple servers you must make it so that they can all access the same information (otherwise with 5 servers a user could only see the content posted to the server they are currently connected to or approximately 20% of the content.) To achieve the data sharing, all of the computers with the software for the website will connect to the same database on a different server. This makes it so all the content is shared across all servers. But now we've introduced a new bottleneck where the database must be updated or read from on every request. This is where this can get slow or even stop when the database is not able to handle all the requests. Typically, a write operation like posting or upvoting is considered more computationally "expensive" than a read operation (e.g. browsing posts or comments). We tend to measure a server's load by its slowest component which is typically data access. Database software is built by some very smart people over time and have a lot of math involved to make them efficient but sometimes software like lemmy can write data in a way that the database algorithm isn't well designed for, making it harder to read the database if you add too much information. Alternatively database software can have inefficiencies appear once enough data is entered in their database.
There is some work that can be done to make load less impactful like: having separate databases for writing and reading and/or cloning data into multiple copies of the database, or designing the way that the data is entered into the database that makes it easy to retrieve.
Fahrenheit is Celsius - 32 then divided by 1.8 which is not an easy conversion luckily its also 9/5ths
The trick I found out was to subtract 32 from Fahrenheit then divide by 9 then multiply by 5.
The other trick, you subtract 10% from your Celsius times by 2, then add 32 but this one doesn't reverse well because you have to add 1/9th