Skip to main content

Calculating size of User and Cache storage


user storage:-

it can be solved using same scenario as mentioned in first article .

 https://tech.nazarmubeenworks.com/2019/08/basics-of-system-design-chapter-0.html


Suppose there are 12 Million of users are adding every year meaning 1 Million per month.

So if we consider 5 year there will be around 60 million of users. Now in terms of data we can look to our DB table and get information about it. A user will be generally having name , id , address , some forien keys .

Lets assume 10 columns with each column on an average storing 4 byte of data.

10*4 = 40 bytes of data for one user.

60 * 10^6 * 40 = 2400 * 10^6 = 2.4 * 10^9 = 2.4 GB of data we need to store only user values.

Also while calculating storage for the user there is also one important point we need to remember is of ids. If we are going to have 60 Million of users which means 60*10^6 users so unique id’s will be

as we know below figures are almost equal

2^10=10^3
then 60*(10^3)^2 = 2^20 *2^6

which means we almost need 26 bits for storing ids. If we have any separate system to generate these ids then 26*60*10^6=1560*10^6=1.5 GB approx.

Cache storage :-

calcluting an idea for cache storage is not tough once we have an idea of calculating total storage . Cache normally sits between end user and application servers and caters read requests for the website. Nearly 60-80 percent of users do not apply any modification to the data of website and just read data. To avoid load on application servers which are modifying data for write requests and involve in lot of performance on data we use cache servers which just caters data as a replica of original one. So if we have 500 GB of original data , 100 GB of data can be served through cache.

There can be multiple techniques we can use for cache such as LRU , LFU which i will explain in coming articles.


Labels:

Comments

Post a Comment

.

Popular posts from this blog

Best LeetCode Lists for Interviews

Here is a list of some of the best questions asked in interviews:-  Must do 75 https://leetcode.com/list/5hkn6wze/ Must do 60  https://leetcode.com/list/5eie1aqd/ Must do medium:-  https://leetcode.com/list/5xaelz7g/ Must do Easy:-   https://leetcode.com/list/5r7rxpr1/ Graph:-  https://leetcode.com/list/x18ervrd/  Dynamic Programming:-    https://leetcode.com/list/x14z0dxr/  FaceBook interviews:- https://leetcode.com/list/xyu98pv6/  Amazon Interviews:-  https://leetcode.com/list/5hkniyf7/  Google Interviews:- https://leetcode.com/list/xyu9xfo1/ https://github.com/nazarmubeen/TopProblems/blob/master/README.md
1 comment
Read more

Career in software engineering : Roles to know

when someone starts a career in software engineering there are plenty of options. Although most graduates have the same degree, everyone starts in a different role. Developer / Coder - Engineers in this role get a chance to actually implement and write software. At the start of a career mostly it is about fixing defects in existing software then taking small changes to the software and eventually getting to the point to handle and implement more complex changes.  Quality analysts / Quality engineers - Engineers in this role test and automate software. This is a challenging role where one has to know about the full functionality of the software and test accurately so the software built is of high quality. This role also involves the automation of test cases and preparing a test suite that can be run and detect issues automatically. Release Engineers - Once the software is built and tested release engineers are responsible for pushing a set of code to production. A production is a ...
Post a Comment
Read more