10 Nov
2009
10 Nov
'09
4:22 p.m.
Is there a limit to the number of files that can be attached to an XWiki
page? If a page has 199 attachments, would it cause any problems or
issues?
** Mary Ellen
10 Nov
10 Nov
4:32 p.m.
Hi Mary Ellen,
On Tue, Nov 10, 2009 at 4:22 PM, MaryEllen Coleman <mea(a)us.ibm.com> wrote:
Is there a limit to the number of files that can be attached to an XWiki
page? If a page has 199 attachments, would it cause any problems or
issues?
More than the total number of attached files, it's the size of those files
that might be an issue. Each time a new document is added a new version of
the page is stored on the database, that has a copy of all the other
documents currently attached to itself. Meaning that if each of your
attached files is 1MB, your total page size is 200MB and each time you add
an attached file it becomes a bit heavier. Once it becomes really big
operations on that page start taking a lot of time and consume a lot of
memory resources.
To make it short: it will work if you've got a big computer on the backend
but it's not recommended.
A better solution would be to create a new page for each file and list all
the pages you've created (since XE 1.8 you can use a space homepage for
this).
Guillaume
** Mary Ellen
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
--
Guillaume Lerouge
Product Manager - XWiki SAS
Skype: wikibc
Twitter: glerouge
http://guillaumelerouge.com/
4:46 p.m.
On Nov 10, 2009, at 4:32 PM, Guillaume Lerouge wrote:
Hi Mary Ellen,
On Tue, Nov 10, 2009 at 4:22 PM, MaryEllen Coleman <mea(a)us.ibm.com>
wrote:
I'm not sure this is right.
Attachments are not loaded when the doc is loaded (only the list of
attachment is loaded which is a single query to the DB to get the
names) so you can have as many as you want I believe. It's only when
an attachment is manipulated and thus loaded in memory that it takes
up memory space.
Now I haven't tested it for real so I don't really know.
Can someone with more experience qualify this answer?
Is there a limit to the number of files that can be attached to an
XWiki
page? If a page has 199 attachments, would it cause any problems or
issues?
More than the total number of attached files, it's the size of those
files
that might be an issue. Each time a new document is added a new
version of
the page is stored on the database, that has a copy of all the other
documents currently attached to itself. Meaning that if each of your
attached files is 1MB, your total page size is 200MB and each time
you add
an attached file it becomes a bit heavier. Once it becomes really big
operations on that page start taking a lot of time and consume a lot
of
memory resources. To make it short: it will work if you've got a big
computer on the
backend
but it's not recommended.
A better solution would be to create a new page for each file and
list all
the pages you've created (since XE 1.8 you can use a space homepage
for
this).
This is pretty cumbersome and I wouldn't recommend it.
Thanks
-Vincent
Guillaume
> ** Mary Ellen
> ______________
4:52 p.m.
On Tue, Nov 10, 2009 at 16:46, Vincent Massol <vincent(a)massol.net> wrote:
--
Thomas Mortagne
On Nov 10, 2009, at 4:32 PM, Guillaume Lerouge wrote:
Yes attachment content is loaded on demand, when you load a page you
get only a list of attachments names.
Hi Mary Ellen,
On Tue, Nov 10, 2009 at 4:22 PM, MaryEllen Coleman <mea(a)us.ibm.com>
wrote:
I'm not sure this is right.
Attachments are not loaded when the doc is loaded (only the list of
attachment is loaded which is a single query to the DB to get the
names) so you can have as many as you want I believe. It's only when
an attachment is manipulated and thus loaded in memory that it takes
up memory space.
Now I haven't tested it for real so I don't really know.
Can someone with more experience qualify this answer?
Is there a limit to the number of files that can be attached to an
XWiki
page? If a page has 199 attachments, would it cause any problems or
issues?
More than the total number of attached files, it's the size of those
files
that might be an issue. Each time a new document is added a new
version of
the page is stored on the database, that has a copy of all the other
documents currently attached to itself. Meaning that if each of your
attached files is 1MB, your total page size is 200MB and each time
you add
an attached file it becomes a bit heavier. Once it becomes really big
operations on that page start taking a lot of time and consume a lot
of
memory resources. To make it short: it will work if you've got
a big computer on the
backend
but it's not recommended.
A better solution would be to create a new page for each file and
list all
the pages you've created (since XE 1.8 you can use a space homepage
for
this).
This is pretty cumbersome and I wouldn't recommend it.
Thanks
-Vincent
Guillaume
> ** Mary Ellen
> ______________
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
11 Nov
11 Nov
8:27 p.m.
Some WEB-INF/xwiki.cfg settings that might improve performance w/r/t
attachments (note the uncommented portions):
...
#-# Whether the document recycle bin feature is activated or not
# xwiki.recyclebin=1
#-# Whether the attachment recycle bin feature is activated or not
storage.attachment.recyclebin=0
#-# Whether the document versioning feature is activated or not
# xwiki.store.versioning=1
#-# Whether the attachment versioning feature is activated or not
xwiki.store.attachment.versioning=0
#-# Whether the attachments should also be rolled back when a document is
reverted.
xwiki.store.rollbackattachmentwithdocuments=0
...
Corollary questions for the list:
(1) When these are set, do the issues raised by Guillaume still apply?
(2) Other than the obvious change of not having attachments change when
rolling back documents, are there any other
side-effects or caveats in using the above custom settings for a Xwiki
instance?
(3) What about the same performance question, but regarding comments
"attached" to documents. Is the main performance impact coming from the
total size of comments, or from the number of comment objects attached to
documents? (Of course comments are limited to 64K so the size issue is
somewhat self-limiting).
Niels
http://nielsmayer.com
PS: Ms Coleman -- Could you please disable your "away" mail reminder
program from bouncing to the list? Thanks.
[xwiki-users] AUTO: MaryEllen Coleman/Poughkeepsie/IBM
is out of the
office. (returning 11/04/2009)
5520
days inactive
5521
days old
4 comments
5 participants
participants (5)
-
Guillaume Lerouge -
MaryEllen Coleman -
Niels Mayer -
Thomas Mortagne -
Vincent Massol