On Monday 22 August 2005 16:22, LurfysMa wrote:
> Is there a good way to estimate what how much bandwidth a web-based
> application will use?
What duration of visits? How many bytes per page? (ignoring cache) How many
visits? These are the most important questions, but you have not given
information about it.
> I am developing an interactive application and I would like to get a
> rough idea how much bandwidth it is likely to use so I can estimate
> hosting costs.
> The application will put up a screen of information initially. Then
> when the user gets started, it will put up a new screen every time the
> user responds -- which will be about 10-15 times a minute on average.
applications already use the technique because:
* it saves bandwidth
* it is quicker (no refresh)
* data resides on the server
* keyboard interaction can easily be added (JS)
> The screens are very similar. Most of the information is the same.
> There are several text boxes whose contents will change and a few
> graphics that will change slightly (like a progress bar).
It sounds like you should definitely look into AJAX. There is no point in
refreshing the entire page if very little changes. Not only would you save
bandwidth ($), but your visitors will be happy with the speed too.
> Is that enough information to estimate bandwidth?
> PS: I accidentally posted this to alt.paidwebhosting, sorry. Cursor on
> wrong line.
Hope it helps,
Roy S. Schestowitz "The speed of time is one second per second"