Support » Plugin: DecaLog » 2.1 Update slowed site to a crawl

  • Resolved lprent

    (@lprent)


    I’d added this plugin on a recommendation from the simple history plugin. Not quite sure what the benefit is.

    Did an update on this plugin to 2.1 this morning and my site slowed to a crawl. After looking at the other possible culprit W3TC and finding that it wasn’t the problem, I disabled decalog and the site sprung back into life.

    Can’t give any more details than that – have to head to work.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Pierre Lannoy

    (@pierrelannoy)

    Hello @lprent and sorry to hear that.
    Could you just tell me what type of logger you’ve created in DecaLog so I can help you to solve this issue?

    Plugin Author Pierre Lannoy

    (@pierrelannoy)

    I’m closing it due to inactivity.

    Don’t hesitate to reopen it if needed…

    Thread Starter lprent

    (@lprent)

    Sorry. Missed the first reply.

    I really can’t give any more detail. There was nothing obvious in the logs, php, syslog, or site. There wasn’t anything obvious in top or df.

    To solve the issue, I just looked looked at elimination strategy through the recent plugin updates and disabled them one at a time – DecaLog was the second.

    I also disabled Simple History as that was the plugin that said to use DecaLog. Reenabled SH as it showed no issues, then reenabled DecaLog – problem returned. Turned off Deca, and reenabled W3TC cache and everything remained running.

    Left the site to the other authors and moderators and went (late) to work.

    I have no idea what the Simple History plugin was using DecaLog for. But did a brief scan of the code now, it looks like it has a logging abstraction. I’d need to look at the DecaLog API to see if SH is using it directly. SH does seem to search better with DecaLog enabled.

    I turned DecaLog back on on the next release and haven’t had problems. Now running on version 2.3.

    The system is semi-dedicated up-to-date ubuntu running on a 8 core Ryzen 1700 server, 48GB RAM and the whole web site runs on a dedicate mdadm raid 1 (I also checked drive array). No other applications were having issues – just slow responses in the php7.4 fpm.

    Plugin Author Pierre Lannoy

    (@pierrelannoy)

    Ah thanks.
    The good news is it’s working now…
    I will get an eye on “Simple History” to understand what they do in their code 😉

    Thanks for the hint.

    eskapism

    (@eskapism)

    Hi! Author of the Simple History plugin here. I can’t find any references to DecaLog in my plugin code and I can’t see that I mention DecaLog anywhere. So I find it confusing that @lprent says that my plugin recommends decalog or that my plugin somehow uses decalog..? Any chance you could explain?

    • This reply was modified 2 months ago by eskapism. Reason: Fix link
    Plugin Author Pierre Lannoy

    (@pierrelannoy)

    Hello @eskapism !
    From my part, I have not reference to your plugin in my code too…
    I must admit, I don’t understand very well what’s going on 😉
    Maybe, @lprent, could you tell us more about who recommend you DecaLog (and why) to help us understand the exact problem you want to solve?

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.