Database Size HUGE !

[Mike Smith]

Hello All - 

Just wondering if someone with a longer history than I with ResourceSpace could give me an idea on what I should expect for database size ? I have seen some comments about loading the entire DB into RAM but I think the DB we are working with that is becoming impractical. Our DB is currently about 14GB, the file store is just under 7TB, with about 100K unique resources in it, most of these have previews and quite a few have alternative files so maybe 300K total files total. We do collect and input quite a bit of metadata maybe 70 fields total and most of those fields are completed with quite a few terms. Many of the fields are indexed. 

My question is, is 14GB normal ? Could this be suspect, and if so any thoughts on where I should go looking first to slim down this chubby DB ? 

Thanks in advance 

MS 

  

[Mike Smith]

Hey All - 

I did a but more digging and found where the giant point are in this DB first I was mistaken it will be quite a bit larger than 14GB it is going to end up more like 25GB. 

Here are the reasons ( or tables ) as to why it is so large. I am not 100% sure what I should be doing here but this seems excessive. 

daily_stat = 2.4GB / Index 5.9GB / 31,000,000 entries 

keywords = 630MB / Index 1.1GB / 10,000,000 entries

resource_keyword = 5.3GB / Index 16.2GB / 99,000,000 entries 

Thoughts anyone ? 

Thanks 

MS

[Allison M Stec]

Have you run database_prune recently? It should reduce some of the db size.

The config "$log_resource_views" could be a contributing factor to the size of daily_stat if turned on.

Partial indexing could be making keyword and resource_keyword large.

If you've got a lot of users or a lot of resources or RS has been in use for some years then these table sizes may be normal.

--
ResourceSpace: Open Source Digital Asset Management
http://www.resourcespace.org
---
You received this message because you are subscribed to the Google Groups "ResourceSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
--
ResourceSpace Developer
Reseller of Colorhythm's Prismpoint Portal DAM

[Dan Huby]

Hi Mike,

The data itself checks out given your row count, I think those sizes are normal. However the indexes are a little crazy but that's just down to how ResourceSpace configures the database out of the box. I think it's a little heavy on the indexes.

We think it's possible for the system to work just as well with fewer indexes. If you're willing to experiment and have a test system handy, you could try dropping the following indexes:

 - Everything except 'stat_day_activity_ref' on daily_stat

 - Everything except 'rk_all' on resource_keyword

That should radically reduce your database usage, and shouldn't (in theory) affect system performance. It would be good if you could try that out and let us know how it goes. You need to check searching generally and also that the graphs still generate quickly in 'Team Centre' -> 'View statistics'.

Dan