This page already takes 22 seconds to parse and is 830KBytes, that is adding stress to the servers every time a logged in user access it.

For the monthly view, you should only include the page title, not the full page.

If you really want one page showing it all, you should add an additional layer to view deletions requests per week.

saibotrash wrote:

(In reply to comment #1)

This page already takes 22 seconds to parse and is 830KBytes, that is adding
stress to the servers every time a logged in user access it.

For the monthly view, you should only include the page title, not the full
page.

If you really want one page showing it all, you should add an additional layer
to view deletions requests per week.

Then the servers are too slow. ;-) There is good use for this page and I hope you do not mean that we are no allowed to put load on the servers for working? Is load only allowed for readers?

(In reply to comment #2)

Then the servers are too slow. ;-)

Nope, you're just pushing to the limit. Even if we expand the limit, people will immediately start inventing other reasons to peg the servers even harder. It has to stop somehere. Please don't reopen just because you disagree.

Saibo > that page is indeed putting to much load on the server. That is why we have a limit, to avoid a couple of pages taking all the resources.

The page listed above really need to be split, that will make it easier for everyone (readers, editors, admins and servers of course).

saibotrash wrote:

(In reply to comment #3)

Nope, you're just pushing to the limit. Even if we expand the limit, people
will immediately start inventing other reasons to peg the servers even harder.
It has to stop somehere. Please don't reopen just because you disagree.

Why shouldn't I reopen if I think the bug is not resolved? Sounds right - there is no formal closure by admins here (like at Wikipedia/Commons deletion discussions).

(In reply to comment #4)

Saibo > that page is indeed putting to much load on the server. That is why we
have a limit, to avoid a couple of pages taking all the resources.

What means "too much"? Do you have numbers in a sense of CPU time? Which percentage of the total CPU time does this page account for?

The page listed above really need to be split, that will make it easier for
everyone (readers, editors, admins and servers of course).

A split will make it not easier regarding a full text search of all open requests of this month using the browser's built-in search.

It seems to me the page creation is not really efficiently done here.