Shutdown job taking _enormous_ amounts of time.

  • Qliphoth

    (@qliphoth)


    8 years ago

    Out of curiosity, I decided to add my entire webserver (Apache, PHP 5.6.19) to a monitor over at NewRelic, just to see what kinds of things were happening, and I was very surprised to see the result. Out of the top ten time consuming jobs, shutdownstands out as the BY FAR largest. This is how much time the jobs have spent over the past 24 hours.

    2,330 sec – shutdown
    484 sec – the_content
    298 sec – w3_cdn_cron_upload
    183 sec – init
    165 sec – do_feed_rss2
    124 sec – do_feed_podcast
    75.8 sec – the_content_feed
    62.9 sec – rss2_item
    45.6 sec – the_title_rss

    I’ve been trying to figure out what it is about the shutdown job that is taking so much time and where it’s being called, but I can’t seem to figure it out. Any hints or suggetsions?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Mark Ratledge

    (@songdogtech)

    8 years ago

    Probably this:

    https://developer.wordpress.org/reference/hooks/shutdown/

    which “Fires just before PHP shuts down execution.”

    Thread Starter Qliphoth

    (@qliphoth)

    8 years ago

    Yeah, I know what the shutdown job is, but I’m trying to figure out why it’s taking so long… 🙂

    Mark Ratledge

    (@songdogtech)

    8 years ago

    Because shutdown “Fires just before PHP shuts down execution”, it sounds like it runs each time a PHP process dies. Add up the total of all the other WordPress functions in that log and compare that to the shutdown total.

    NewRelic is high-level logging. For a better idea of what your server is doing, take a look at the actual server logs and the number of PHP processes and average loads via the command top. Monit is a good low level GUI server utility to use to get profiles over time drawn from commands like top.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Shutdown job taking _enormous_ amounts of time.’ is closed to new replies.