Why capacity planning ?

[aminer]

Hello,

Question:

But what is the purpose of the capacity planning using the queuing theory ?


Answer:

You have to be very carefull, if for example you are using a database
with your webserver and you are accessing this database from internet or
intranet and you are doing reads and writes and deletes transactions on
this database and after that the data of the databse is served through
internet or intranet , as i told you you can use a worst case scenario
cause the database queing node has an hyperexponential on its service
side, so you can choose the worst case scenario, so if the reads takes
much more time than the writes and deletes, you have to choose only the
rate of the writes transactions , the rate means how many writes per
second, as your lambda, but notice with me that the network node or the
intranet node of your network is markovian, so if for example the
bandwidth of your network internet connection is 30Mbps, since it's an
M/M/1 markovian queuing node that means that the bandwidth will be
reduced by 50% cause the Knee of the M/M/1 internet network queuing node
is reached at 50%, and don't forget also
about the TCP/IP protocol overhead of ~20% , so you have to be carefull
when you do capacity planning..

And why you have to do capacity planning ? cause if you must
ensure a quality of service and set a constraint on the maximum waiting
time, let for example say 5 seconds for each internet user to receive
it's webpage, you have to do capacity planning to set the maximum number
of connections ofyour webserver correctly and do your analytic queuing
network calaculations or you queuing network simulation.



Thank you
Amine Moulay Ramdane.

[aminer]

I correct please read again...

Hello,

Question:

But what is the purpose of the capacity planning using the queuing theory ?


Answer:

You have to be very carefull, if for example you are using a database
with your webserver and you are accessing this database from internet or
intranet and you are doing reads and writes and deletes transactions on
this database and after that the data of the databse is served through
internet or intranet , as i told you you can use a worst case scenario

cause the database queuing node has an hyperexponential on its service

side, so you can choose the worst case scenario, so if the reads takes
much more time than the writes and deletes, you have to choose only the

rate of the reads transactions , the rate means how many reads
transactions per second, as your lambda, but notice with me that the

network node or the intranet node of your network is markovian, so if
for example the bandwidth of your network internet connection is 30Mbps,
since it's an M/M/1 markovian queuing node that means that the bandwidth
will be reduced by 50% cause the Knee of the M/M/1 internet network
queuing node is reached at 50%, and don't forget also
about the TCP/IP protocol overhead of ~20% , so you have to be carefull
when you do capacity planning..

And why you have to do capacity planning ? cause if you must
ensure a quality of service and set a constraint on the maximum waiting
time, let for example say 5 seconds for each internet user to receive
it's webpage, you have to do capacity planning to set the maximum number

of connections of your webserver correctly and do your analytic queuing
network calculations or your queuing network simulation.