[wp-testers] RC3. Click on Links menu item returns out-of-memory error

[Waldo Lydecker]

There are 26 posts. It's really just a test install -- my "production"
WP install runs 2.9.2 and is reasonably stable.

I have not observed any other pages to have failed in this version RC3.

(Prior to RC3 I had been using some nightly builds of RC1; at that
time, auto-update would make Apache go nuts, spawning dozens of
processes; but -- happily -- RC3 has not, so far, provoked such
activity.)

By the way, your advice:

> generally idles at 12-15 MB, perhaps an extra few meg
> if you're running a localized version, and then plugins of
> course will add to that depending on their weight,
> optimization, and performance.

is the most explicit, succinct -- and helpful -- statement about
memory limit management for WP that I have seen.

This helps now for WP3; It would have very helpful had such a nicely
phrased bit of advice were in the documents for the previous version 2
of WP. It seems to me that the docs have been a bit murky and
non-committal about when to adjust the memory, and how much. Without
sample-case guidelines, a lot of trial-and-error was required, and it
was a painful and time-consuming episode I shall not soon forget.

May I go one step beyond the scope of this discussion?

The real nightmare -- for those of us who have the ability to set up
and adjust Apache -- is the lack of any rules-of-thumb or explicit
guidelines for how best to adjust the Apache config and MySQL configs
to run a plain-vanilla LAMP and a plain-vanilla WP install.

Getting that right took days and days -- and I still wonder whether my
guesses are really in the right range for a modest installation for a
WP site that serves a modest number of visitors. My server is
reasonably stable now, but I really don't imagine that I have adjusted
it to what would work best for WP. Some examples of good server
configs (with focus on WP installs) would be great.

It seems to me that a sane discussion by WP specialists on Apache
config and MySQL config, etc., would help a lot of persons to get
started faster and keep their WP installs running well.

I've been running my own LAMP+WP for a couple of years, and I *still*
would feel better if I had some good guidelines from WP.org of what
works for just for WP. As it is, I have had to sift through vague
general advice about adjusting Apache and MySQL for all purposes, and
make wild guesses about what works best for just WP.

Perhaps you could pass this along to someone who writes the docs. …

Thanks

Waldo

On Mon, Jun 14, 2010 at 1:20 AM, Andrew Nacin <wp at andrewnacin.com> wrote:
> On Mon, Jun 14, 2010 at 4:05 AM, Waldo Lydecker <
> waldo.lydecker at cinemaminima.com> wrote:
>
>> Upgraded site from WP v 2.9.2
>>
>> Links: 99. No links imported
>>
>> Plugins: All (52) | Active (27) | Recently Active (1) | Inactive (25)
>> | Drop-ins (1)
>
>
> We have a default memory limit of 32 MB (64 MB for multisite). WordPress
> generally idles at 12-15 MB, perhaps an extra few meg if you're running a
> localized version, and then plugins of course will add to that depending on
> their weight, optimization, and performance. In this case, it sounds like
> you simply pushed the limit. I doubt the code on the links page is high in
> terms of memory usage at only 99 links. Assuming you have a lot of content,
> do you have other pages failing?
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>