[@kshirtcliffe Member 13 years, 2 months ago]

@echiomega I’d be really interested in hearing if that works. I remember it causing me a great deal of stress.

[@kshirtcliffe Member 13 years, 2 months ago]

That just prompted me to search my inbox for the problem so this is what I wrote a few months ago when I was having that problem :
====
If you’re using pretty permalinks then you have to start it with a numeric identifier like %post_id% or %hour% anything with a number in.

%postname% on its own is fine for small sites but wordpress has a bug which sends it into database mental town for big sites.

Just putting %post_id% in and updating all the links has reduced me from 1300queries to 37.
=====

Maybe even WP3 has solved the problem, to be honest, I’m one of the people who forgets about things the minute they get sorted.

[@kshirtcliffe Member 13 years, 2 months ago]

@echiomega My site has literally thousands of pages and the first time mine was eating memory it was due to a wordpress bug with the permalinks (various strange sql queries going into infinite loops) – try changing the format of your permalinks.

I’m not sure it’ll make a difference but worth a go?

[@kshirtcliffe Member 13 years, 3 months ago]

I know this isn’t terribly helpful for this situation, but I have just reverted back to 1.2.10 and the memory problems have gone away. For now, I can live without the upgrade. It might not solve the problem @echioMega, but I suppose it is nice to know there is an alternative to needing and infinite amount of memory for now…

Is returning to the old version an option for you?

[@kshirtcliffe Member 13 years, 3 months ago]

Just to note, I’m also experiencing buddypress using 1.5 eating memory. My site is terribly slow at the moment.

When I disable buddypress, my site becomes lightning fast again. Specifically, when I installed I get :

“The plugin generated 1 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.”

Did you have the same message echiomega?