Thread

Hi there,

We have quite a big problem with the exp_relationships table. It can get up to 6gb some times and it is quite hard to manage.

Moreover when we edit any article the table gets locked with the update to the relationship entry and the site basically goes down.

Do you have any solution for this? Is there a way to prevent the DB cache to be stored on this table?

We are not using Playa just the native EE relationships module.

Thanks

Hi, jkmedia.

Can you tell us which version/build of EE2.x you’re using? See EEWiki:// HowTo Determine My EE Version

the newest version of Playa now uses its own table, but that might not be the issue here. How many entries do you have?

We are using EE 1.7.0 build 20101018.

We are not using Playa and we have 184858 entries.

Thanks

jkdmedia,

Can you give us an idea of how you are using relationships please?
How many weblogs? Which use a relationship and how you are approaching it in your templates

You can set EE to clear your cache every-time you create a new entry if that helps

We have around 15 weblogs and I am not really sure what do you mean by how are we approaching the relationships.

Is there a way to disable the cache at all?

Reviewing the DB log the problem seems to be this query “UPDATE exp_relationships SET rel_data = ‘’,
reverse_rel_data = ‘’”, which is the cache being cleared right?

I am not sure if it’s best not to clear the cache at all or just not have a cache.

Hi jkdmedia,

Approximately how many entries with relationships do you have? Go ahead and try clearing all caches during a low traffic period and see if there’s any change.

Cleaning the cache is exactly what locks the site. If I do wait, while my site is down, until the cache is completely clean it is back up to a huge size the following day.

Is there any way to disable that cache?

I am not aware of a way to disable this caching. This looks like a datbase (optimization) issue. Have you asked your db administrator for assistance? There might be a few tweaks that can help.

Yes, I have no one seems to have an answer for this. Do you know any way to optimize this table?

Thanks

jkdmedia,

Not that table specifically but for overall performance of your db there are some excellent tips in this document