BIG table ps_jm_pagecache

[petrixstar]

Hello All!

I tried to export to the database and it seems I couldn't!then I exported from vps via putty ssh and it worked and it seems that the table ps_jm_pagecach has 160mb and 18235000 lines. Does anyone know what is with this table and if I can delete it, that is to empty it?

Thank you very much for the answer

[4presta]

Hi.
This is a question for the page cache module author.

[petrixstar]

ok, thanks, I found the module I also have spoken with the developer, I solved it, he told me that I can delete the table quietly!

in the meantime I found another table : ps_page_viewed has 21 Mb and 400k rows. can it be emptied? I did not find anything concrete on the forum and on google

Thanks

[4presta]

hi
ps_page_viewed is used for backoffice and graph display.
Yes, you can empty it, but don't remove it.

[Rizzzle]

Can we delete ps_jm_pagecache?

Mine is 11gb

[4presta]

SQL

TRUNCATE TABLE ps_jm_pagecache;

 

[Rizzzle]

Thanks for the quick reply please can you write a basic description on how to do that in phpmyadmin?

 

Thanks

[4presta]

Open the database, select a table, find SQL at the top, write a query in it and click the "save" button.

 

https://wpengine.com/support/run-query-phpmyadmin/

Edited July 11, 2024 by ps8modules.com (see edit history)

[Rizzzle]

Hi,

Thank you. The table that is huge is ps_jm_pagecache_bl

Is this okay to TRUNCATE?

 

Thanks

[Rizzzle]

And ps_jm_pagecache_mods

Thanks

[scfrancis]

Hello,
I allow myself to relaunch this topic, because I also have huge bases:
ps_jm_pagecache_bl
ps_guest
ps_jm_pagecache_mods
ps_jm_pagecache
Do you have any information for the ps_jm bases, what module is it please?
Can I empty them without risk?
Thank you for your help

[Rizzzle]

Perhaps ps8modules could answer our query? Thanks 

[JPresta.com]

I just discover this post, sorry.

In order to reduce the disk space consumption of the cache I recommend running a purge periodically (every 2 or 3 days). A purge deletes the cache of pages that no longer exist or whose context no longer exists. This does not affect cache performance. You can perform a purge manually via a button below the cache statistics table, or by scheduling a CRON job with the URL displayed in the "API (CRON URLs)" menu of the module configuration. 

When you have no choice you can reset the cache like this:

TRUNCATE TABLE jm_pagecache;
TRUNCATE TABLE jm_pagecache_contexts;
TRUNCATE TABLE jm_pagecache_details;
TRUNCATE TABLE jm_pagecache_bl;
TRUNCATE TABLE jm_pagecache_mods;

You can also safely delete files in /var/cache/pagecache

Be aware that this is not to do periodically, only if you are blocked.