Open GoogleCodeExporter opened 9 years ago
http://shadoura.com/stuff/core.18075
Original comment by Andrew.Shadoura
on 2 Jun 2010 at 9:51
Attachments:
Issue 20 has been merged into this issue.
Original comment by mcc...@gmail.com
on 2 Jun 2010 at 10:41
This is an artefact of the way Wub handles request contents. It loads them all
into
RAM, even 'file upload' artefacts.
It's hard to know what to do about this, short of possibly determining that a
given
content is either of file upload, or is very large, then dumping them to disk.
I'm open to suggestions.
Original comment by mcc...@gmail.com
on 2 Jun 2010 at 10:43
Current thinking is that the RAM available is too small to accept this size
upload ... as strange as it seems, 10x overhead isn't unexpected.
Next thought - to save interactions over a certain size, then process them from
disk may fail because tcllib's mime package may not (probably doesn't) process
things without loading them from disk ... so we gain nothing in terms of RAM
footprint.
Original comment by mcc...@gmail.com
on 8 Jun 2010 at 8:11
Original issue reported on code.google.com by
Andrew.Shadoura
on 2 Jun 2010 at 9:47Attachments: