ntemple

I found the same warnings during our audit and came here looking for an update to debugbar. Hoping that @lupusmichaelis patch can be merged and we’ll have an update soon that is fully compatible with WP 5.7/5.8

Maybe the SDK should simply use a default of us-east when not passed?

Actually, Don’t remove the define() … you need to add the define AND update the PHP settings.

WP defaults to lowering the memory limit 40M unless WP_MEMORY_LIMIT is defined. See:
https://github.com/WordPress/WordPress/blob/master/wp-includes/default-constants.php#L35

Agreed there are three separate (yet interrelated) issues:

– High CPU usage
– High Memory Usage
– Bots spidering everything

And you are correct, I am somewhat “confusing” the issue, in part because they all have similar symptoms.

We, too upgraded our VPS, but that only helped for a little while. Due to various circumstances, I’m unable to provide specifics at this time.

@valpreston numbers definately help, thanks!

@nicola.peluchetti Please contact me at nick [at] nick temple dot com and I can provide additional specifics.

Unfortunately, we’re seeing memory issues on the front-end as well. It’s causing the site to die with OOM errors even when no one is using the back-end. Raising the memory limit in PHP fixes this, but then …

On a VPS like at Hostgator, when the system overall uses too much memory, the system just kills Apache (as there is no swap).

@mjhale Well said and much more diplomatically.

The problem happens whenever pages are hit, whether that’s by a spider or a human.

By blocking spiders, you are essentially decreasing traffic your site, which is why it seems to make things better.

However, whenever people hit the problem pages, the plugin still runs out of memory rendering those pages.

Focusing on bots, then, is somewhat of a red-herring – though there is a separate, duplicate content issue with allowing all events to be spidered.

We need to be focusing at the causes of the memory issues. The fact all events are loaded on some pages is a point in the right direction.

Can anyone pinpoint what release changes to the plugin started causing the issues? Maybe looking at what changed could help, or even downgrading to the last known good version?

@nicola.peluchetti

Thanks, please do add the note about what the code does. Many people, desperate to find a solution (as I am) will blindly copy & paste code without understanding what it does.

In this case, the disclaimer is necessary, as we have many non-technical very creative people reading the forums.

As you said, the problem is not with the bots, it’s with the memory usage of the plugin in part caused by the loading of all posts.

And … I think there is a core memory management issue in the plugin (bug), as this problem was introduced within the last few updates.

I do appreciate the time you’ve spent tracing down the problems, your insights have been very useful in helping me to fix my sites. Thank you.

@nicola.peluchetti

Completely de-listing your entire site from Google, MSN and Bing by blocking access to their spiders – because of bugs with the event calendar? No, thanks!

Dear reader: please do not use the code above unless you want your site to simply disappear from all major search engines.

-1

Mark,

Absolutely – we’re working on updates for data, as well as display various sports, and something really special I can’t announce for a few weeks.

I *might* have the NBA done by the 20th 2013; and it’s cutting things close. If not this year, we plan to have a fully line up in 2014.

BracketPress is currently a finalist in the VentureSharks (https://www.venturesharks.org/) competition on May 1st, 2013 – which we’re preparing for.

Assuming BracketPress wins, we’ll be releasing updates pretty quickly, as I’ll be able to work pretty much full-time on the next stage of the project.

If we don’t win, then the updates may take a little longer longer, but are happening.

Yes, tried that, and it helps a little in that fewer pages are being indexed by search engines (is that really a good thing?!), so fewer requests to the server.

The underlying problem, however, isn’t the number of pages being indexed (“good” bots like google generally are pretty good about not pounding servers).

The core problem is that with the most recent updates, each page is taking way too much memory and CPU to generate individually.

Same problem here. I have two sites using All-In-One Event Calendar and they taking down the server with CPU usage and out-of-memory errors

I’ll take a look at the spider usage pattern as well, I hadn’t thought of that.

It’s even worse with the Hostgator VPS, because when the max memory is allocated, the system just kills the Apache process, killing _all_ sites on the server.

Can we expect a resolution to the resource issues soon?

If a moderator is available, is it possible to move this thread out of reviews and into support? Thanks – Nick

I’m assuming that you’d like to just display 16 teams, and not all 64.

Is this correct?

For the bracket view, there isn’t an easy solution at moment. The system is currently hardcoded for the 2013 NCAA Division 1 Men’s College basketball tournament, aka March Madness, and is displaying all 64 of the primary teams.

Once the season is over, we plan to go in and update the plugin to work with other tournament types and extend the display options.

Glad to here that it’s working for you!