Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.


If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping


Answers may be delayed for posts that do not include sufficient information.

Database size

I just wanted to check and see if our database size is indicative of a problem. We have just under 12,000 items in our database, and the MySQL database is approaching 5GB. Does that sound right?
The reason I ask is because our web host, pair.com, took the database down last week, saying it violated their policy. This took me by surprise, since their policy is, apparently (per the page they directed me to - I'd never heard/seen anything about this), that MySQL databases must be under 200 MB! This struck me as insane, because even our small drupal sites have databases in excess of 200 MB, and heaven knows our CollectiveAccess database has been more than 200 MB for YEARS (on the same host). We've since moved our installation to a VPS with additional storage. 

Comments

  • To give you some data for comparison, we have a CA installation with the following (these numbers were gathered from the dashboard widget):
    • 128674 objects, 
    • 75965 entities,
    • 661 places, 
    • 2289 occurrences, 
    • 37523 collections, 
    • and 5677 object representations.
    Our database is around 10 GB, in wich 9,7 are from the "ca_sql_search_word_index" table. 
    Maybe our search_indexing.conf settings are a little overkill...
  • When there are many entries in your system it might make sense to use ElasticSearch for indexing rather than SqlSearch.
Sign In or Register to comment.