Automattic / Automattic/wp-super-cache

Using "Trash" takes a long time

Open
#913 0 comments 0 reactions 0 assignees View on GitHub
[Plugin] Super Cache bug
Dominant language
PHP
Stars
436
Forks
130
Avg merge
15h 11m
Merged PRs (30d)
10

Description

I have a site with over 20K posts and when I trash some post, I see that the time it takes is very long. I suspect (but am not sure how to check it) that this is because the trash operation triggers some sort of cache cleaning that takes a long time.
Could there be a feature that would stop or restrict any cache operation triggered when deleting or modifying posts?
(if it's already available, I apologize for asking it here, and would appreciate the pointer)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by reproducing the slow Trash operation on a site with more than 20K posts and determine whether cache cleaning is involved. Done would require a clearly scoped way to stop or restrict cache work triggered by deleting or modifying posts, along with verification of the resulting behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.