Vista - ftpwebrequest: Upload is slow...

Hi,

I just tried uploading files with the ftpwebrequest class. I find that
they are really slow. However I am not sure if this is because of
me... I am writing everything to the input stream byte by byte so that
I can calculate the progress. However I only calculate only after 1024
bytes have been uploaded. Is there a better way to do this?

Moreover are there any general property settings for the object so
that ftp uploading is at least faster relatively speaking...

--deostroll

"deostroll" <deostroll@xxxxxx> wrote in message
news:c6ffd1d7-5ba1-4435-bc66-560dbf14dd62@xxxxxxYou can still calculate progress percentage if you use large byte blocks,
such as 1024 bytes. Percentage is still bytes sent divided by total bytes.
You just incriment the bytes sent by the block size, rather than by one.
This may not be your problem as to speed, but it may help.

--
Mike

On Jan 4, 5:20*pm, "Family Tree Mike" <F...@xxxxxx> wrote:I notice that the cpu usage goes to 100% while I do uploads! Is this
normal?
--deostroll

"deostroll" <deostroll@xxxxxx> wrote in message
news:b6202b3d-5f15-4fd0-b8db-89e3f8bcac8f@xxxxxx
That doesn't sound right, but it's hard to tell without seeing your code why
that might occur.

--
Mike

On Jan 4, 9:58*pm, "Family Tree Mike" <F...@xxxxxx> wrote:The high CPU usage is probably high because of creating/destroying a
progressbar control. I've written a custom class for a datagridview
progressbar column. Here while "painting" it so happens that I create
a new progressbar control and draw its image in the cell meant to show
the progress updates. Probably this is why it happens...

Is it normally supposed to be slower than using ftp.exe? Why is this
so?

--deostroll

"deostroll" wrote:This "sounds" like you are creating a new progress bar in each repaint. I
hope that is not what you meant...
I ran a few comparisons of ftp.exe versus the async upload code example at
http://msdn.microsoft.com/en-us/libr...ebrequest.aspx

It's true that the timings are somewhat slower (~40%) using the async
upload. If you are seeing times increase significantly in your code, I would
look at running your upload code in a console app to eliminate any issues
with your UI update logic.

Mike

On Jan 5, 11:01*pm, Family Tree Mike
<FamilyTreeM...@xxxxxx> wrote:As such the ftp-ing (and other stuff) happen on a separate thread in a
synchronous manner. The UI update is asynchronous. But its not a
direct UI update. I am updating a datatable. My datagridview is bound
to the datatable. However I synchronize the updates to this table.

If I adopted the async solution how will I get the progress updates?

--deostroll

"deostroll" wrote:
Sorry, I did not mean to imply trying the async method. I was just trying
to point out an existing example and the speed of that example relative to
ftp.exe.

If your upload times are significantly more than the ftp.exe (like a factor
of two or more), then it is likely beneficial to time your upload code
outside of any UI. If the upload code runs resonably well away from any UI,
then you've narrowed the areas you need to review in your code.

Mike

"Family Tree Mike" wrote:
I should have added, that if you wanted to use the code I referred to above,
you could just add a PercentComplete property to the FtpState class and
monitor that value from some other part of the code which updates the UI.

Mike

On Jan 6, 6:26*pm, Family Tree Mike
<FamilyTreeM...@xxxxxx> wrote:Hi,

Is this the correct way to upload via batch?

for (i = 0; i <= TotalChunks; i += 1024)
{
//Console.WriteLine(i);
ftpStream.Write(fileContents, i, 1024);
ftpStream.Flush();
}
ftpStream.Write(fileContents, 0, fileContents.Length);
ftpStream.Flush();

----------------
Is Flush() known to cause an overhead?

--deostroll