Hi,

I use a CouchCMS installation as a backend application. The size of the database is quite large. I do not need cache and neither fulltext search.

How can I remove fulltext data and cached data to reduce the size of the database? I tried to change the editables to searchable='0', but it had no effect.

Any idea?

Regards,
Olliwalli

[KK]

Olliwalli,

If you think a large database (the fulltext table) would have any kind of performance issue, it's a non-issue really.
If you have disk space consideration, that is not expensive any more.

So, I wouldn't advice you to tweak with the core tables. The data is used by Couch at several places and you could end up breaking things in unexpected ways.

Thanks.

[trendoman]

What is the size of db? Before it hits 2-5gb it's ok and can fit into RAM of average webserver.
I also have this issue (50 million records in couch_data_text) and the reality is that I stopped caring about it. It is by design, that's it. No way to disable it without changing core couch code.
I think I discussed it among other design things with @KK and reality is that CouchCMS is for certain type/size projects. If you need a solution that cares about your big project, as well as mine and others, some would perhaps advise for us to team up and make a custom build and constantly support it with other improvements. Do you have time for this? I doubt it

Hi Trendoman

My db is actually very small compared to the sizes you mentioned. I just wonder what the option searchable='0' means and what its effect is on the database. When setting up a new installation with all editables set to searchable='0', will the fulltext table be empty or be reduces in size?

Regards,
Olliwalli

[KK]

@olliwalli

I just wonder what the option searchable='0' means and what its effect is on the database.

It means precisely what the term suggests - the editable region will no longer be searchable (through both <cms:search> as well as the custom_field parameter of <cms:pages> tag).

When setting up a new installation with all editables set to searchable='0', will the fulltext table be empty or be reduces in size?

If all the regions are set to 0 for searchable, then the fulltext table will still have a record each for every cloned page in the system but these records will be empty (no searchable data) - so the table will not be empty but its size should go down considerably.

You mentioned 'new installation'. The same thing will happen for existing installations also where searchable was on to begin with but was later turned off - the only catch is that the fulltext record for a page would reflect the new status only when it is saved afresh.

Hope this answers your query.