I am trying to deploy an oC instance back at work but...in like two days our DB almost exploded (the image isn't so far from reality).
In fact, we want to use it solely to map our shared FS which is about 1Pb.
I quickly stopped it while it was indexing the whole thing, purged everything, deactivated versioning, launched it anew and now, it don't grow as fast as before but still..
19-Feb-12_15 : 7625244672 : 7.2G
20-Feb-09_24 : 10359930880 : 9.7G
22-Feb-09_30 : 12398362624 : 12G
23-Feb-09_37 : 15267266560 : 15G
28-Feb-11_01 : 15976103936 : 15G
01-Mar-09_03 : 17599299584 : 17G
02-Mar-10_08 : 19218300928 : 18G
02-Mar-13_50 : 20019412992 : 19G
05-Mar-09_00 : 23920115712 : 23G
With just 5 users on it who have created one or two shares each then stopped using this oC instance, oc_filecache table kept growing.. +4Gb during last week-end without anyone logged even once.
The thing is, i have 500+ users so.. occ files:scan --all can't be used, it would take definitely way too long to gain not so much (actually trying it on my 5 test users and it's already too long).
I guess making some cron with a "truncate table" wouldn't be recommended ?
Have anyone informations / advices / a rope ? (sorry, bad joke but i'm kinda desperate about the next meeting with my boss on that topic).
Thanks in advance !