HTTPort Frequently Asked Questions Products
SDK
FAQ
Forum
Download Contact
Donate
powered
with
BOA
Q: Why is my connection so slow ?

When using "Remote Host" mode, the connection is by all means slower then the direct connection. Much slower. So, even if you have a full T1 at your disposal, don't expect that high bandwidth from the tunneled connection.

First, see whether you are using your own or privileged HTTHost server (see "Use personal host at" fields). If these fields are blank, this means that you are using a free public server, and have neither registered nor installed your own personal server outside. In this case you are being served by a server which is serving 100s of users at the same time, and the pipe and other resources are limited. Therefore public server IS SLOW. Some may say - VERY slow, but it is how it is. You need it faster - either register or install your own personal server on your own hardware and feed it and keep it happy. The personal software is free, and is NOT a limiting factor in this case.

Then, you are using a personal or privileged server. You may think of 22 KBytes/sec. as of the higher limit. Actually, it's 22 KBytes times N where N is a number of HTTP requests per second. Assuming a proxy won't get more than one full HTTP requests per second, including all the timeouts, lags and response delays, that would be it. 22K is the amount of raw tunneled data that HTTPort can fetch with a single request from the HTTHost server. For those of you who know what Base64 is - 22k * 4 / 3 is close to 32k. Now, see what timeouts your HTTHost is set to. Privileged hosts are set to 0:1:2. The first timeout (0 = no timeout) is activated whenever there is plenty of tunneled data upon every request. This is true with streaming/downloading for instance, but is NOT true when there is a lot of small data portions sent back and forth. Therefore your tunnel must be loaded up high for this timeout to get in work. In case the load is not that high, timeout 1 (sec) is activated, and HTTPort will not issue another request until 1 sec. interval expires. Here is your 22k/sec. limitation. Anyway, talking about the happier 0 timeout - the next request will be started immediately, therefore estimate how many requests per second can your proxy and network handle, each request delivering up to 32k of text. This would be your limit. By "network" I mean also the pipe HTTHost is running on, because the HTTHost side of the pipe sees the doubled throughput - raw data and tunneled data. See the "Statistics" page in HTTHost.

Why is it so ? Because the key design principle for HTTPort was to closely mimic regular HTTP traffic - a stream of standard GET requests each of which returns an HTML page. This limits both the upload and download speeds for HTTPort, but it's one of the by-design tradeoffs.

As a bottom line - you need it fast - register or install your own HTTHost. You need it even faster - this is unfortunate, but nothing can be done really.
Bandwidth and support provided by
Quantum Silicones Inc.
HTTPort products family is written by Dmitry Dvoinikov
(c) 1999-2006 Dmitry Dvoinikov