A big one I've seen unfortunately too often is loading entire files (or even entire object graphs with an ORM) into memory unnecessarily.
In the old days of the web you would read and stream objects, but some common APIs today make it just easier to load up everything in RAM. So loading 100 MB in RAM may not sound like much, but if you have a thousand users doing that it's going to bring your system down.
Learn to stream large things rather than building up giant things in RAM. This includes JSON, serialized objects for the cache, files, reports, etc.
Thanks for the informtion...πππthis is what differentiate a coder from programer.. Having a deeper understanding of how the software affects teh RAm is an added advantage. You will now how to scale up your application. Stay blessed @aminmansuri
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A big one I've seen unfortunately too often is loading entire files (or even entire object graphs with an ORM) into memory unnecessarily.
In the old days of the web you would read and stream objects, but some common APIs today make it just easier to load up everything in RAM. So loading 100 MB in RAM may not sound like much, but if you have a thousand users doing that it's going to bring your system down.
Learn to stream large things rather than building up giant things in RAM. This includes JSON, serialized objects for the cache, files, reports, etc.
Thanks for the informtion...πππthis is what differentiate a coder from programer.. Having a deeper understanding of how the software affects teh RAm is an added advantage. You will now how to scale up your application. Stay blessed @aminmansuri