• Resolved maomaohu

    (@maomaohu)


    When we run a scan, the most prominent usage of time comes from something called “Wink Bedug Crap”. A Google search for that turns up a few pages about bed bug poop and nothing else. I’m pretty sure we don’t have any “Bedug Crap” installed, nor do we have anything to do with the company called Wink DebugMode.

    Do you know what this is? Is it an internal reference to something else?

    Here’s a picture of our results:

    View post on imgur.com

    https://www.ads-software.com/plugins/p3-profiler/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter maomaohu

    (@maomaohu)

    It’s probably important to mention that we’re using a multisite installation from WPEngine.

    Plugin Contributor Kurt Payne

    (@kurtpayne)

    This is not internal. It might be part of a must use plugin. The name is pulled from the standard WordPress plugin header. Please contact wpengine support with further questions.

    Hi this is wink, of “wink debug crap”, I am unclear as to how that plugin has come to be installed on your system, but please uninstall it. It is a plugin I sometimes use for debugging issues at WPEngine, it should definitely not be running in a non-debug situation. Are you currently hosting at WPEngine?

    Thread Starter maomaohu

    (@maomaohu)

    Hi Wink, thanks for solving this mystery. We are indeed hosting at WPEngine, and have had some plugin issues in the past. That may be why it’s installed. I went ahead and deleted your plugin.

    Unfortunately now only P3 shows up:

    View post on imgur.com

    Much as I would like to pretend our plugins make no net impact on page load time, that seems unlikely.

    We are running a multisite installation and P3 comes up under /wp-content/mu-plugins. Could it be that P3 is only profiling the must-use multisite plugins?

    Plugin Contributor Kurt Payne

    (@kurtpayne)

    Hi maomaohu,

    This (only P3 showing up) can sometimes happen with certain opcode caches. eaccelerator (used by wpengine) has been known to cause this type of behavior.

    Please keep in mind that interference with P3 isn’t bad, it’s just incompatible … these extensions do good things by optimizing things, it just makes it harder to profile.

    Thread Starter maomaohu

    (@maomaohu)

    So does this mean we are unable to use P3 to profile our plugins?

    Plugin Contributor Kurt Payne

    (@kurtpayne)

    Hi maomaohu,

    Possibly. You’ll need to contact your host for further information. PHP extensions operate at a lower level than P3, so they have more power / control over the way PHP behaves. P3 can’t really do anything about that.

    Hi Maomaohu, Kurt is exactly right. Any opcode caching will interfere with P3’s ability to profile. However, you have two things you can do (1) Contact customer support and request a performance analysis on a specific url. This analysis will give you a list of slow functions/plugins or (2) Contact customer support and ask them to disable eaccelerator so that you can run the profiling plugin … however, you’ll probably want to have them turn it back on after you have completed your analysis so that you get the performance benefit provided by it.

    Cheers,

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘What is Wink Bedug Crap?’ is closed to new replies.