Hello Tomcat users
I am using TC 5.0.28 on a machine with an AMD Athlon 3000+
(not particularly strong, by current standards)
I use an applet for uploading, which uses
(pretty much) something like
httpsOutput = httpsUrlCon.getOutputStream();
OutputStream bos = new BufferedOutputStream( httpsOutput,BUFFER_SIZE );
while(true)
{
i = bis.read(byteArray,0,BUFFER_SIZE);
if( i == -1 ) break;
bos.write(byteArray,0,i);
bos.flush();
totalBytes += i;
if( totalBytes >= fileLength ) break;
}
httpsOutput = httpsUrlCon.getOutputStream();
OutputStream bos = new BufferedOutputStream(
httpsOutput,BUFFER_SIZE );
(fairly standard: BufferedOutputStream, etc. on client side,
and pretty much the reverse equivalent on the server side -
InputStream bis =
new BufferedInputStream( request.getInputStream(),
BUFFER_SIZE );
Point is:
On my local area network, the client can send to the server
at about 1 Megabyte a second.
But, for example, from a remote location, residential clients are
bandwidth-upload limited - even with Cable modem - to about
50,000 bytes a second due to the asynchronous configuration which
broadband vendors impose on their hardware. That is, 50,000 bytes
up / but 600,000 bytes download - most people download all the time,
after all.
(I guess as Point-to-point becomes more popular, this will change.)
I don't know if any of this helps, but I thought I would mention all this
to see if it gives any perspective on the situation.
Maurice Yarrow
Leon Rosenberg wrote:
So you effectively measure the ability of tomcat to throw away your
bytes and send you an error page. That doesn't make really sense, does
it?
Leon
On 6/22/06, CMSuser <[EMAIL PROTECTED]> wrote:
Leon Rosenberg-3 wrote:
>
> sorry, maybe i'm misunderstand a whole bunch of things here, but what
> exactly is your "appropriate url"?
>
> I mean, you can test download speed by accessing your own servlet or
> even static content, ok, but you can't upload anything without having
> a receiver for it.
>
> leon
>
I'm very new to this "web" stuff. What I did to get started was
installed
the Tomcat 5.5.15 and copied one of the sub folders in webapps folder
and
named it "abc".
in the web.xml in the conf folder , set the readonly to false.
after that I just did a "put" from the client.
eg. curl -T "file.txt" http://191.168.1.1:8080/abc/ . (This was what
gave
low throughput).
or with my java client, it's :
PutMethod pm = new PutMethod(url + "filename");
.....
then I use HttpClient to executed the above putmethod. (this give's good
throughput ).
My guess is that the curl client itself was the bottleneck previously.
However the same curl client gave better upload speeds with other
webservers(Apache), so it's confusing.
regards,
Aman.
--
View this message in context:
http://www.nabble.com/file-upload-speed.-t1816944.html#a4987102
Sent from the Tomcat - User forum at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
