|
|  |
Wireless Data Services and Mobile Multimedia
392 hits
| Jan 27, 2005 10:01 pm |
|
re: re: How Do You Become a WiFi Hotspot?....Here's Some Simple Tips |
Michael Lemm
 | |
Hi Tony,
I asked my friend Ken about your question....this is what he said:
==== I quit using "rules of thumb" some time ago because of the number of variables I kept encountering.
What I do now is breakdown the specific applications used in a particular environment into tasks, assess the client, server, and communications aspect in completing each task, and then forecast where bandwidth will become an issue. Along the way I develop a small number of user profiles since there are frequently differences by job as to how often particular tasks are done. With this, I can predict performance for a given set of users over various types of communications infrastructure. I suggest you take a similar approach.
I find more performance issues with the data structure, server architecture, and client platforms than with communications. If communications is only 10% of the total performance issue, it is foolish to focus 90% of the resources on "fixing" the communications. However, that seems to be the approach taken by most companies. There are a couple of things I have found to be almost rules. For any given application, performance levels off somewhere between 200 Kbps and 780 Kbps. Adding bandwidth once the level is reached shows no user perceived improvement in performance. 40 Mbps via a serial communications port (Ethernet, modem) is the current top transfer rate for most data centers - 2 servers, no other traffic, full duplex, and 100 Mbps pipes. The reason is that this is where the ability to process the traffic through the IP stack tends to max out. Client machines tend to have even lower maximum capability. There are some very expensive and application specific custom build servers that will take advantage of higher bandwidth, but these are rare.
As for terms like "high" and "average", I find these almost useless without knowing the context. A system for warehouse inventory has significantly different traffic and performance needs than a medical records department, for example. Both differ from a location supporting casual users at an airport terminal.
A quick sanity check is possible if you know of a similar environment in terms of applications and tasks where you can do some traffic analysis. Even a short term trace using a data analyzer will give you something to judge by.
====
Feel free to contact Ken for help if you like. He's a great guy, consumate professional, and a wealth of expertise.
http://www.ryze.com/view.php?who=khilving
God Bless, Michael
----------------------------------
> Tony Gatto wrote: > Is there any way to determine how many users you can have on a specific amount of bandwidth. I know it has to do with the way it's used...size of files...etc...but is there any benchmark? If I told you I had a pipe that is 2MB down and 512k up....is there a generic way to determine how many user there can be if it is made into a hot-spot? I'm working on a unique project that will have that kind of bandwidth. The upload use will be high and the download average. > >> Michael Lemm wrote: >> >> For those considering establishing a WiFi hotspot.......residential or business.......to allow VoIP enabled voice transmission via WiFi or just stand alone net access.......below will give you some basics to mull over. >> >>I'll try to keep this as simple as possible. >> >>Here's some simple ideas you should consider for becoming a WiFi Hotspot. >> >>* To turn your business into a hotspot, you really only need 2 things: >> >>- Hotspot Kit (which should include hardware, software, and remote monitoring) >> >>- High Speed Internet (whatever is appropriate for your situation....DSL, T1, or DS3 connectivity) >> >>* Before you order your hotspot kit, you need to first determine what type of service you will need: >> >>- Single Access Point >> >>OR >> >>- Multiple Access Point >> >>The number of connection points you need is determined by the amount of area that you wish to make available for wireless internet access. For example......larger hotels will require one access point per every 20 rooms (on average) while a coffee shop can adequately service their clientele with just a single access point. >> >>* The last decision you will need to make is whether or not to bill your clients for wireless internet access. Today, more and more enterprises are offering wireless internet access as a value-added service in an effort to attract more visitors to their hotels/shops. In today's competitive environment, offering complimentary hot zones can be the determining factor when customers weigh your offering against that of your competitors. >> >>However, should you find that billing your customers is what you want to do, find a provider who can help you do that. Your hotspot kit should come with software that will enable you to take credit cards right over your gateway (the page the users 'see' when they try to access the web using your hotspot). You'll likely partner with that provider in that revenues would be shared by both you and "them". Thae provider you choose will make sure the hotspot is running efficiently. This allows you to focus on your key business and to receive a profit-share check each and every month your customers log on to the net in your hotspot. >> >>The above is a simplistic description of what you'll need to think about before becoming a WiFi hotspot. Do your homework along these lines and you'll have a decent foundation to make a good business sense decision. >> >>Regards, >>Michael Lemm >>FreedomFire Communications >>http://ShopForVoIP.com/?mscprez >>http://ShopForWiFi.com/?mscprez >> >> Private Reply to Michael Lemm (new win) |
|