Amrayu78 Yeah, I can see the problem. I am very sorry to hear that you are experiencing such problems. I don't know what happened, but the site is slowing down more.... Even in the admin panel I often get 500** errors that say that the server is overloaded. Also while working I am often redirected to Cloudflare - am I human? Maybe it has something to do with-- I don't understand why VDS can slow down so much.

The people page is not the highest loaded page, it only has two Views on it. During testing, I noticed that the slowdown is most caused by accessing intermediate post fields, ( slow queries from Toolset) and the relationship between person and Drama/Movie/Special.

I've adapted as much as possible a view that displays all related posts to the current person, that's all I can do unfortunately. After these optimisations I have seen a slight improvement in the loading of people pages. We can't change the pagination settings as we need to display the All tab items, it wouldn't make much sense. I am a bit disappointed in the speed of Toolset and in my future projects I will avoid using it unfortunately ((

Max Romanchenko: Thanks for explaining Max. I'm not sure what else I can do to make things faster. Cloudflare is supposed to make the site faster because we have a lot of bots attacking. I have to leave it on for now so we don't get bombarded by bot scripts.

For people pages, I noticed the load gets better if I do not fully display everything for the all tab and if I used pagination it works okay. Should I go to Toolset's forum and ask them about this issue? Maybe they have some better way?

I've been monitoring the server's load whenever it slows down drastically and most times I see multiple "people" pages being hit which makes the site slow down a lot. Through trial and error and after fixing the people's view for all, it got a lot better.

Amrayu78 Thank you for the information, Duong. Yes, I think you can post the problem on the Toolset forum, maybe the support will advise something.

Although I think they will advise something like this:

However, I don't think these tips will help you much, but it's definitely worth a try.

I'm really sorry I can't be too helpful with this....

Max Romanchenko: Thanks Max.

I have some questions to your comments.

Amrayu78 Hi Duong,

The ideal would be to simplify things so much that you don't use relationships at all. But that doesn't sound realistic, as everything has to be done from scratch.....

Relationships (many to many) are quite difficult to implement in Wordpress. A person can be in different films and different films relate to different people. It's a classic many-to-many relationship. The difficulty is that the relationship also keeps the fields, what exactly was the role of the person in this film.....

So the question is where to store the person's role in the Drama? In the Drama? Not quite right? In the People post? Not either. So Toolset uses an intermediate table (that's ok) in the database to store this data. Apparently therein lies the problem somewhere.

Difficulty 1. Storing relationship fields, it causes a slowdown.

Difficulty 2. Many types of posts in a relationship with a person (drama, movie, special). It would be much easier if it was a single post type, like "Title" and drama, movie, special would be its categories. But it's impossible because everything needs to be redesigned....

The simplest thing would be caching. Other options are quite difficult or impossible without redesigning the structure of the site.

Toolset provides a quick start so that everyone can do what they want without a deep understanding of what's going on under the hood. That's ok. but when time passes and the data starts to grow, problems appear....

Sorry for a lot of text and not much of a solution. Yes, I can try to defeat the Toolset and use a custom solution to store this relationship data. But that won't be compatible with the forms for adding / editing people to tittles.

So this problem is open.

Max Romanchenko: Thanks for your detailed explanation. I think I understand the issue. Any ideas on how we should cache the people pages then?

I have CloudFlare cache and also OPCache on the database level turned on. If you know of a way to enable this for people pages specifically, please let me know.

Thanks.

Amrayu78 As far as I know cache can't be enabled only for certain pages. It works the other way round. By default caching works for all pages of the site, but you can exclude some pages from the cache.

OPCache is a good option, this type of caching speeds up php processing, leave it enabled, but it's not enough. You need a full-page cache. Try playing around with the caching rules from CloudFlare.

The second option is an object cache (like Redis). This will require additional software to be installed on your server. This is a more complex way, since all requests are cached in RAM when the page is first generated, and then served to the user from RAM and not from the database. I think a full-page cache is easier to start with.

However, do not forget that full-page caching has a big disadvantage - it is outdated content. Users will not always see the latest changes and changes they just made. This may add some confusion...

Max Romanchenko: Hi Max, There's a way to cache URI path in CloudFlare.

I've set the following rule in CloudFlare for now:

People Cache rule:

When incoming requests match...

Then...

Edge TTL

Browser TTL