High memory usage

Ok, I`m the lucky owner of a : Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 35063540 bytes)
which implies that the sitemap tried to allocate aprox 75 MB of memory, 35 over the alloted one. Is there any way to decrease and optimize the sitemap generator ? Smaller amounts of urls per file ? Need suggestions.

Regards,
Adrian A.

Hello,

try to disable "generate text sitemap" option, remove files from vbseo_sitemap/data/ folder and regenerate sitemap.

Would that disable generating yahoo sitemaps ?

Tried it, still not working.

Yahoo supports xml sitemaps now, you don't need text sitemap for them.

What exactly is the error you get?

SECTION START] tags [9,012.7Kb mem used] [197,085s (+879s)]
[create sitemap file] filename: sitemap_19.xml.gz, number of urls: 1 [9,014.1Kb mem used] [197,085s (+0s)]
[create sitemap index] filename: sitemap_index.xml.gz, number of sitemaps: 19 [9,022.6Kb mem used] [197,085s (+0s)]

Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 35063540 bytes) in /xxxxxxxxx/vbseo_sitemap/vbseo_sitemap_functions.php on line 1298

Looks like you did not disable text sitemap option OR did not remove files from data/ folder before generating sitemap. Please double check that.

Well it worked now. I just deleted *.gz and the sitemap was created. Is that enough ? Reason why I`m asking is I have about 1.2 mil posts and this shows : 661,013 total urls ...

if you aren't including showpost itself, that sounds fine. the sitemap should link threads (all pages) and anything else you want

That`s the problem, I have show post, show thread, forum display set.

Well I did some changes now ... and I see the sitemap being generated and using about 9 MB per sitemap created.

Do you get more URLs included now? Note that private (not visible to guests) forums are NOT included in sitemap.

Yes. The main factor was disabling the smart show post option.

I see. That option excludes showpost pages from sitemap in case if thread contains only a single post.

Well hopefully this will have solved my issues.