Make WordPress Core

Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#28068 closed defect (bug) (invalid)

Bug when you create a very large page

Reported by: shady3's profile Shady3 Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.9
Component: General Keywords:
Focuses: Cc:

Description

Hello!

I have a large page (with 6.000+ links to all the posts of my blog) and since the moment I installed Wordpress 3.9, it started to give me High (very very high, CPU usage).

I tried it on a new 3.9 wordpress installer, on 2 differents hostings, and with all default themes.

I say this is a bug because if you try to post the same page on wordpress 3.8, it will wotk correctly.

I have nothing more than this links in this page. At the moment I delete this webpage, CPU usage drops and website going fine.

I have tried it with no plugins installed.

Attachments (1)

TODOS LOS LIBROS NP.php (1002.2 KB) - added by Shady3 12 years ago.
Page

Download all attachments as: .zip

Change History (5)

#1 @Denis-de-Bernardy
12 years ago

  • Keywords reporter-feedback added

Any odds you copy/paste the page in a txt or html file, and attach it for reference so devs have material to work on?

@Shady3
12 years ago

Page

#2 @Shady3
12 years ago

Thanks a lot for your response, I attached the page that is giving me this error.

May be if you post it on any server and visit this page some times, you will see this bug.

#3 @DrewAPicture
11 years ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Anytime you're dealing with this amount of content you're going to see slowdowns in terms of the ability to edit or view it, this is just a fact.

Case in point, the attached file took upward of 5 seconds to load in my browser on fast internet. This problem falls outside the scope of a core issue.

#4 @miqrogroove
11 years ago

I agree there was no traction here. If there was a specific regression identified in 3.9 then we would be more likely to fix it.

Note: See TracTickets for help on using tickets.