[Owncloud] filescache concept for large sites

[Craig Sawyer]

I'm not sure where putting them in their own sqlite DB will save you much,
since you still have OC clients checking in to the server all the time.

You will definitely need to build indexes against the queries coming in
from ownCloud-core. In my install, there is no indexes at all.  You might
need a few owncloud servers to handle the load I'm not sure.  I haven't
done any load testing, but it definitely seems to be IO intensivewhich
makes sense).  So you will want to put the file store on good fast disk,
etc.

I am very curious how your scale out goes, we aren't quite your size, and
have a much slower roll-out schedule, but so far we are handling the load
ok.  Since we don't have the resources to do extensive testing, we just
slowed the roll-out schedule down a lot, so we can test and monitor as we
roll-out and fix things as they come up. (we are rolling out about 1 user a
week right now).

-Craig

On Thu, Apr 11, 2013 at 11:23 PM, Andrzej Kwiatkowski <
andrzej.kwiatkowski at gmail.com> wrote:

> Hi,
>
> We are preparing to use OC in very large instalation (thousands of users),
> for beginning about 20k. Our main problem is how OC or PgSQL
> will work with filecache table where if every user will have 1000 entries,
> in this table will be 20 mln records.
>
> I don't know if there is possible not to have central filecache,
> but for every user in datadir in sqlite db ?
>
> I've also found in db structure that there is no way to connect entry
> from oc_storages to user ? Or i'm missing something.
>
> Regards
> AK
> ______________________________**_________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/**listinfo/owncloud<https://mail.kde.org/mailman/listinfo/owncloud>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20130412/ab8fe2f2/attachment.html>