Julian Pietron | 11 Apr 2012 15:57
Picon
Favicon

File uploads onto slow file systems/storage hardware


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hallo,

we recently experienced some problems when uploading (large) files (>=30
MB) with cherokee: After a part of the upload has completed, a 500
Internal Server error is issued to the browser and the connection (and
upload) is terminated. These problems only occur on an embedded board
with a Cortex A8-ARM processor and a very slow NAND memory (where the
file shall be stored to). For file corruption prevention, the file
system (ext3) on this NAND is mounted in sync mode so that no data is
buffered in RAM but anything is written directly to NAND. Even if async
mode is used instead, the error occurs after some more time (probably if
the kernel's I/O buffer is full). cherokee delivers the upload to a
backend application attached via FastCGI.
My question is: Is there anything within cherokee that may cause such a
behaviour, if e.g. the backend application needs to long to handle the
request (because the file has to be stored to NAND before the request is
handled), or is it all the fault of the backend application? Are there
any configuration values in cherokee that may influence this behaviour?

Thanks,
Julian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPhY2vAAoJENidYKvYQHlQY3sQAJB/btJ0kuqiDvBdQ1S1VZiq
(Continue reading)


Gmane