• xmetman

    (@xmetman)


    Hi

    I have a problem with cron slowness.

    Yes, the cron scheduler is running.

    I wish that I could send you a screenshot of what I see in the WP-Control screen.

    Nearly all entries in it have amber exclamation marks against them.

    I can’t see how I can drill into the cron events to tell you more.

    All I can say is that at the top of the page it states “One or more cron events have missed their schedule” and usually that’s at least a dozen of them.

    As an example I have Jetpack installed which fires off to any subscribers when I post a new blog. That could take two days or more to return an email to me (the only
    subscriber at the moment) I imagine this is a cron event that is responsible for this.

    This may not be directly related to cron but when I try and add widgets to a sidebar that goes smoothly until I try and update and save the changes which can take several minutes to complete and more often or not fails.

    I did remove Jetpack entirely thinking it was that but the slowness was still reported by WP-cron.

    When you look at the site externally it works pretty fast and you wouldn’t think you had a problem:

    I hope someone can figure out what’s causing this slowness and fix it.

    Bruce

    • This topic was modified 2 years ago by James Huff. Reason: redundant link removed

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • threadi

    (@threadi)

    You can upload a screenshot at any image service and post the link here, e.g. at https://imgur.com/

    Note that WP’s own crons are triggered by requests. If there are few requests, even if you change setting or uninstall responsible plugins, open crons can still take some time to process.

    You could also switch from WP-Cron to Systemcron. Then it runs independently of requests to WordPress (and also speeds up your website). More details here: https://kinsta.com/knowledgebase/disable-wp-cron/

    Thread Starter xmetman

    (@xmetman)

    This is all getting a bit beyond me!
    I’ve been blogging with WP for ten years and never had an issue like this.
    I’ve reinstalled and reverted to a backup.
    I’ve disable all plugins even removed Jetpack and still WP-cron reports issues.

    Here’s the latest – the top ten are all showing amber !

    jetpack_sync_cron
    None 2022-12-04 11:28:01
    2 hours 30 minutes ago Automattic\Jetpack\Sync\Actions::do_cron_sync() Every 5 minutes

    Select this row jetpack_sync_full_cron
    None 2022-12-04 11:28:01
    2 hours 30 minutes ago Automattic\Jetpack\Sync\Actions::do_cron_full_sync() Every 5 minutes

    Select this row jetpack_display_posts_widget_cron_update
    None 2022-12-04 11:31:25
    2 hours 26 minutes ago jetpack_display_posts_update_cron_action() Every 10 minutes
    This is a WordPress core event and cannot be deleted

    wp_privacy_delete_old_export_files
    None 2022-12-04 11:35:49
    2 hours 22 minutes ago wp_privacy_delete_old_export_files() Once Hourly

    Select this row jetpack_scan_refresh_states_event
    None 2022-12-04 11:46:57
    2 hours 11 minutes ago Automattic\Jetpack\Scan\Admin_Sidebar_Link->refresh_state_cache() Non-repeating

    Select this row jetpack_v2_heartbeat
    None 2022-12-04 12:02:38
    1 hour 55 minutes ago Automattic\Jetpack\Heartbeat->cron_exec() Once Daily

    Select this row jetpack_clean_nonces
    None 2022-12-04 12:09:50
    1 hour 48 minutes ago Automattic\Jetpack\Connection\Nonce_Handler::clean_scheduled() Once Hourly

    Select this row jp_purge_transients_cron
    None 2022-12-04 12:10:04
    1 hour 48 minutes ago jp_purge_transients() Once Daily

    Select this row jp_sitemap_cron_hook
    None 2022-12-04 12:16:20
    1 hour 41 minutes ago Jetpack_Sitemap_Manager->callback_sitemap_cron_hook() Sitemap Interval

    Select this row do_pings
    None 2022-12-04 12:24:17
    1 hour 34 minutes ago do_all_pings() Non-repeating
    This is a WordPress core event and cannot be deleted

    recovery_mode_clean_expired_keys
    None 2022-12-04 14:35:47
    37 minutes 29 seconds WP_Recovery_Mode->clean_expired_keys() Once Daily

    This is a WordPress core event and cannot be deleted wp_update_plugins
    None 2022-12-04 14:35:47
    37 minutes 29 seconds wp_update_plugins() Twice Daily

    This is a WordPress core event and cannot be deleted wp_update_themes
    None 2022-12-04 14:35:47
    37 minutes 29 seconds wp_update_themes() Twice Daily

    This is a WordPress core event and cannot be deleted wp_https_detection
    None 2022-12-04 14:35:49
    37 minutes 31 seconds wp_update_https_detection_errors() Twice Daily

    This is a WordPress core event and cannot be deleted wp_scheduled_delete
    None 2022-12-04 14:37:12
    38 minutes 54 seconds wp_scheduled_delete()
    Grunion_Contact_Form_Plugin->daily_akismet_meta_cleanup() Once Daily

    This is a WordPress core event and cannot be deleted delete_expired_transients
    None 2022-12-04 14:37:12
    38 minutes 54 seconds delete_expired_transients() Once Daily

    This is a WordPress core event and cannot be deleted wp_update_user_counts
    None 2022-12-04 14:37:12
    38 minutes 54 seconds wp_schedule_update_user_counts() Twice Daily

    This is a WordPress core event and cannot be deleted wp_scheduled_auto_draft_delete
    None 2022-12-04 14:37:13
    38 minutes 55 seconds wp_delete_auto_drafts() Once Daily
    Select this row astra_addon_get_addon_usage
    13 hours 3 minutes astra_addon_get_addon_usage() Once Daily

    This is a WordPress core event and cannot be deleted wp_version_check
    None 2022-12-06 06:32:57
    1 day 16 hours wp_version_check() Twice Daily

    This is a WordPress core event and cannot be deleted wp_site_health_scheduled_check
    None 2022-12-08 14:35:47
    4 days WP_Site_Health->wp_cron_scheduled_check() Once Weekly

    Select this row jetpack_recommend_videopress
    None 2022-12-15 12:09:50

    threadi

    (@threadi)

    Check Tools > Site Health to see if there are any anomalies mentioned there.

    Apart from that: WP-Cron is only executed for requests to the site. Therefore, if the site has not had any visitors for 2 hours, no cronjob can be executed. Hence my tip about system cron above.

    If it is not, the cause could also be in your hosting. Contacting the support might also help.

    Thread Starter xmetman

    (@xmetman)

    My Hosting is through NetNerd and they’ve been kinda helpful.
    But the advice I get from them is to move up to multi-hosting (I then get a 100% resources/cpu threshold) or go to cloud hosting (which gives me 125% resources/cpu threshold).

    My reply is how can I be over exerting the CPU with no subscribers or views?

    Here’s the results from the Health Check.

    4 recommended improvements
    Recommended items are considered beneficial to your site, although not as important to prioritise as a critical issue, they may include improvements to things such as; Performance, user experience, and more.

    One or more recommended modules are missing
    Performance
    PHP modules perform most of the tasks on the server that make your site run. Any changes to these must be made by your server administrator.

    The WordPress Hosting Team maintains a list of those modules, both recommended and required, in the team handbook (opens in a new tab).

    Warning The optional module, curl, is not installed, or has been disabled.
    Warning The optional module, imagick, is not installed, or has been disabled.

    A scheduled event has failed
    Performance
    The scheduled event, jetpack_sync_cron, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

    You should use a persistent object cache
    Performance
    A persistent object cache makes your site’s database more efficient, resulting in faster load times because WordPress can retrieve your site’s content and settings much more quickly.

    Your hosting provider can tell you if a persistent object cache can be enabled on your site.

    Learn more about persistent object caching. (opens in a new tab)

    Page cache is not detected but the server response time is OK
    Performance
    Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.

    Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:

    cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.
    Median server response time was 541 milliseconds. This is less than the recommended 600 milliseconds threshold.
    No client caching response headers were detected.
    A page cache plugin was not detected.
    Learn more about page cache (opens in a new tab)

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Cron slowness’ is closed to new replies.