WAFileUploadTag, large uploads, and crashes

>> Subject: Re: [Seaside] WAFileUploadTag, large uploads, and crashes
>> 2008/10/2, Carl Gundel <[hidden email]>:
>>>
>>> Has anyone here had problems with crashes and uploading large files using
>>> WAFileUploadTag?
>>
>> Could you define "large"? On Squeak with something in the region of
>> tens of megabytes: yes.
>
> Ten of megabytes would be about right.  It seems like uploading a 20MB file
> consumes a couple of hundred megabytes of Smalltalk memory.  I wonder if it
> is Web Toolkit to blame, or Seaside.

> 2008/10/2 Carl Gundel <[hidden email]>:
>>> Subject: Re: [Seaside] WAFileUploadTag, large uploads, and crashes
>>> 2008/10/2, Carl Gundel <[hidden email]>:
>>>>
>>>> Has anyone here had problems with crashes and uploading large files using
>>>> WAFileUploadTag?
>>>
>>> Could you define "large"? On Squeak with something in the region of
>>> tens of megabytes: yes.
>>
>> Ten of megabytes would be about right.  It seems like uploading a 20MB file
>> consumes a couple of hundred megabytes of Smalltalk memory.  I wonder if it
>> is Web Toolkit to blame, or Seaside.
>
> Seaside is to blame that it want's to have the contents of the file in
> the memory, that's 20 MB in your case. For the rest it's either
> WebToolkit or the adapter that sits between Seaside and WebToolkit.
> Since this part shouldn't really do much.

> 2008/10/2 Philippe Marschall <[hidden email]>:
>> 2008/10/2 Carl Gundel <[hidden email]>:
>>>> Subject: Re: [Seaside] WAFileUploadTag, large uploads, and crashes
>>>> 2008/10/2, Carl Gundel <[hidden email]>:
>>>>>
>>>>> Has anyone here had problems with crashes and uploading large  
>>>>> files using
>>>>> WAFileUploadTag?
>>>>
>>>> Could you define "large"? On Squeak with something in the region of
>>>> tens of megabytes: yes.
>>>
>>> Ten of megabytes would be about right.  It seems like uploading a  
>>> 20MB file
>>> consumes a couple of hundred megabytes of Smalltalk memory.  I  
>>> wonder if it
>>> is Web Toolkit to blame, or Seaside.
>>
>> Seaside is to blame that it want's to have the contents of the file  
>> in
>> the memory, that's 20 MB in your case. For the rest it's either
>> WebToolkit or the adapter that sits between Seaside and WebToolkit.
>> Since this part shouldn't really do much.
>
> Hmm, that part somehow does not read OK. Lets try again:
>
> Seaside is to blame that it wants to have the contents of the file in
> the memory, that's 20 MB in your case. For the rest it's either
> WebToolkit or the adapter that sits between Seaside and WebToolkit.
> Since this part shouldn't really do that much it's likely that the
> problem is somewhere in WebToolkit. Needlessly Copying data around is
> quite a common problem.
>
> You could give Swazoo 2 a shot.
>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside