On Sat, Jun 12, 2010 at 11:02, Ivan Levashew <[email protected]> wrote:
I'm testing WebDAV now and getting lots of exceptions when copying photos from PhotoAlbum.
There are entries like this one:
Caused by: java.lang.OutOfMemoryError: Java heap space
Web server isn't stable in these moments.
javaw.exe consumes about 600Mb of memory. Although I can adjust it to use 3Gb of memory, this seems to be a wrong way. Storing big attachments in a database is a wrong way. Handling them in-memory is a wrong way. They should be handled in another manner. Some kind of event-based servlet streams attachments block by block without putting any whole octet stream in memory (it seems that stroring attachments in database implies this as a consequence).
No matter what I (and you) do, wrong way will constantly show its wrongness and limitations.
X-Wiki is far from being perfect yet indeed it's outstanding. I don't regret I have spent some time to get it working. I hope, current way of handling attachments will be obsoleted soon.
+1, storing attachments in the DB is a pretty bad idea. Not to mention that storing large objects in MySQL restrains from using InnoDB.
-- If you want to get to the top, you have to start at the bottom
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Je prête mes livres sur Bibale, http://www.bibale.com/bibale/-/user/hbs