Log In
Home
(1 votes) 1:12 am
December 17, 2022
Offline
Hi,
Site Health has started complaining about autoloaded options after I installed CyberSEO. TBH I'm not sure there is a performance hit on my website but it is listed as critical so I thought I'd ask if there is something I'm missing.
I noticed that the options are using almost half of the Total 1 MB that site health is complaining about.
While the site itself hasn't slowed down significantly, I have been getting some 504 errors when pulling feeds.
Login to see the quote
| Option Name | Size |
|---|---|
| xcd | 339.40 KB |
| default presets | 61.15 KB |
| syndicated feeds | 39.83 KB |
| comment authors | 26.95 KB |
| parse feed log | 7.50 KB |
| feed options | 4.30 KB |
1:19 am
July 2, 2009
Offline
It's a plugin's core - the executable code. 1MB of memory can't hurt your site. What's your server configuration? I mean how much memory it provides to a PHP process? E.g. my server handles it just fine. Other customers don't complain about it as well. Do you use a dedicated server?
1:28 am
December 17, 2022
Offline
Thanks for the clarification.
Yes, I'm using a server on Oracle cloud with 12 GB of RAM, so 1MB is nothing, but as I mentioned earlier, I wasn't sure if this was really a critical issue as Site Health claims it is, so thought I'd ask.
I personally haven't noticed any slow downs. Only occasional 504 errors when pulling feeds where the site stops responding.
1:33 am
July 2, 2009
Offline
WordPress simply thinks it's a lot for just an option. I could store it in the database via a MySQL request as some other plugins do so WordPress just won't see it and there will be no warning, but in fact it won't change anything. Also I do consider it's not a good idea to write something into the WordPress database bypassing the API.
As I said above, other plugins write much bigger amounts of data there, but they don't use WordPress API, so WordPress doesn't even know on how hard they use the server's memory and load the MySQL engine...
As about the 504 error, that's because you have to increase the PHP max execution time, since the default one is not enough to wait for all the feeds to be parsed: Login to see this link
Note that on some servers this option may not work and you will have to modify the max_execution_time value in your php.ini file: Login to see this link
1:42 am
December 17, 2022
Offline
Ok, I've set it to 600 as per the image. It was already at 300 seconds, which should have been plenty of time, but I do have some other plugins that manipulate the post after it gets published, so CyberSEO is triggering those plugins after each post too.
Thanks. I'll see how it goes.
All RSSMost Users Ever Online: 541
Currently Online: JoJo
5 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 68
Freedom: 61
Pandermos: 54
MediFormatica: 49
B8europe: 48
Member Stats:
Guest Posters: 337
Members: 2853
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1640
Posts: 8352
Newest Members:
wanmarkets, torontomark48, info.ckmedianetwork, contact.mybeautystar, samuelbodde, john.prushAdministrators: CyberSEO: 3947