>>With a little work, you could probably intercept the upload via groovy, place it on a network drive, replace the attachment with a link to that network file.. <shrug> Would think that this would be your next step? Granted, I've never tested the idea; but it should do what you're looking for. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bjquinn Sent: 29 August 2007 00:49 To: [email protected] Subject: Re: [xwiki-users] Xwiki file and attachment storage
Esbach, Brandon wrote: > > So far my own internal wiki's run at between 5mb and 3gb - with no > real noticable difference in performance from the smallest to the > largest. > Hmmm, yes, the problem seems to be currently that our Exchange database right now is 200gb, filled mostly with all these attachments. The goal was to get those attachments out of the huge, unwieldy 200gb, corrupt-prone, Exchange database. The problem with *any* database on the order of tens or hundreds of gigs is of course (beyond performance) possibility of corruption, and time to backup and restore because it has to be done as one big unit. I was hoping that we could store those attachments as individual files, rather than just moving our problem from a huge Exchange DB to a huge xwiki DB. I know filesystems aren't good at indexing, etc. But attachments are often jpg's and stuff that can't be indexed or anything. -- View this message in context: http://www.nabble.com/Xwiki-file-and-attachment-storage-tf4214945.html#a 12378518 Sent from the XWiki- Users mailing list archive at Nabble.com. _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
