Re: Witango-Talk: HTTP Upload

[Garth Penglase]

I'd be very interested as to whether this is purely a Windows/Witango 
issue or if it relates to OSX and other platforms. I agree that it is 
totally unacceptable that there is anything more than a few 
percentage cpu usage, and this will significantly affect performance 
on my servers when I upgrade to Wi5 in the next week or so, as I have 
a number of apps that will require this service.

Maybe With has a comment on this one....??
Garth
Thats not the issue. The issue is having a solution for a client 
that  is not savvy enough to use an ftp client. I already use webdav 
in such  a way that they could connect with a webfolder from 
windows, or  directly from OS X. But these are people that can only 
be expected to  work with a single interface, and click a few 
buttons. Using HTTP  Upload is very simple and suits that. But HTTP 
Upload has other  problems, and this CPU Usage issue now knocks it 
completely off my list.

Robert.

On Saturday, March 22, 2003, at 05:10  AM, Michael Dittbrenner wrote:

Robert

Why not just put up a ftp server instead of using http. Ftp protocol is
a lot faster than http for uploading and puts less strain on the  server.
Windows 2000 comes with a ftpd built in and if your client doesn't have
a ftp client they can download a trial from like www.globalscape.com  for
cuteftp.
Michael Dittbrenner

-----Original Message-----
From: Robert Garcia [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 22, 2003 6:59 AM
To: [EMAIL PROTECTED]
Subject: Witango-Talk: HTTP Upload
I normally don't use http upload for many reasons, but I had to do a
quick and dirty solution for a client. They must be able to upload MP3
files to our servers. The files range from 10-20 megs. Before I put
this into production, I wanted to test the load it would put on my
servers. My app uses witango to accept the file argument, and write it
to a file where I want it. I am running Witango 054 and IIS 5 on
windows 2000. During the upload, the server pegs 100% CPU usage,
dllhost.exe and inetinfo.exe being the culprits. Witango only spikes
when the upload is done to write the file.
Since I have only used http upload with very small files in the past, I
have never noticed this. This is totally unacceptable. If I upload the
same file to the same IIS Server using IIS WebDav, it doesn't break a
sweat, 1-2% CPU Usage. I can't recall every testing this with other web
servers, does anyone else have any info with apache or Webstar?
It looks like I will have to write a custom desktop app for this
client's admin, which I did not want to do. If anyone knows of any IIS
5 tweaks that may help, I would appreciate it. My systems are
completely patched once a week.
--

Robert Garcia
President - BigHead Technology
CTO - eventpix.com
2781 N Carlmont Pl
Simi Valley, Ca 93065
ph: 805.522.8577 - cell: 805.501.1390
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/ - http://theradmac.com/
_______________________________________________________________________ _
TO UNSUBSCRIBE: send a plain text/US ASCII email to  [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body
_______________________________________________________________________ _
TO UNSUBSCRIBE: send a plain text/US ASCII email to  [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body
--

Robert Garcia
President - BigHead Technology
CTO - eventpix.com
2781 N Carlmont Pl
Simi Valley, Ca 93065
ph: 805.522.8577 - cell: 805.501.1390
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/ - http://theradmac.com/
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
               with unsubscribe witango-talk in the message body


--
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
               with unsubscribe witango-talk in the message body