It took me awhile to find out that you can break the sitemap into chunks and change the chunk size.

On my setup sitemaps crash (lock up MySQL) not only with 10000 chunk size, but even with 1000. So far it works when I reduce it to 300, but I still do not have a good understanding of the pros / cons / parameters of chunk configuration.

I think this should be documented, plus chunk size should be configurable through UI.

Comments

jt6919’s picture

jt6919 commented

so please post - how do you do this?

jt6919’s picture

jt6919 commented

anyone know how to do his for 1.x??

dkruglyak’s picture

dkruglyak commented

There is a hard-coded constant in the module file...

jt6919’s picture

jt6919 commented

that doesn't help - can you tell me specifically where in the module is the code I need to change, and what I need to change it to?

any help most appreciated!

jt6919’s picture

jt6919 commented

I haven't gotten any responses to this at all - if you are reading this and you can help me fix this problem (break the sitemap down into chunks)...

I WILL PAY YOU IF YOU CAN HELP.

Please contact me ASAP.

dkruglyak’s picture

dkruglyak commented

Change the first statement in gsitemap.module, that defines GSITEMAP_CHUNK_SIZE

jt6919’s picture

jt6919 commented

sorry.....I'm using 5.x-1.dev and the 5.x version of this module has no such option. BEWARE - you can't upgrade to drupal 5.x until this feature is included (and have a large sitemap)

dkruglyak’s picture

dkruglyak commented

Actually you can. I simply disabled this module since performance hit is unacceptable and value is dubious.

jt6919’s picture

jt6919 commented

that was my whole point - you can't upgrade to 5.x and have the same features (the ability to break a sitemap down into chunks). The XML Sitemap module for 5.x gives all entries, and you are right - the performance hit and degradation of the server (with more than 10,000 nodes) is absolutely unbelievable.

To FIX the module 5.x and make it configurable to have the index file and sitemap chunks would be of GREAT value (for anyone with more than 10,000 nodes). Otherwise - you can't have a google sitemap and lose CONSIDERABLE search rankings and indexing.

dkruglyak’s picture

dkruglyak commented

I have seen no evidence that this sitemap improves indexing / rankings. In fact my traffic went up after I disabled it.

However it is a nice plaything for diagnostics.

darren oh’s picture

darren oh
Primary language English
Location Lakeland, Florida
commented
Component: Code » Documentation
dkruglyak’s picture

dkruglyak commented
Status: Active » Closed (duplicate)

Duplicate of http://drupal.org/node/79583

jt6919’s picture

jt6919 commented

If you saw no evidence of improved traffic from using an XML Sitemap - then you are doing something wrong, or your site is so small it wouldn't matter anyway.

An xml sitemap:

- gets you indexed in Yahoo! faster, and gets more Yahoo traffic (when you add the feed into Yahoo! SiteExplorer)
- gets you indexed faster and more completely with google (when sitemap is verified in google webmaster tools)

if you got more traffic when you removed it, it was merely coincidence. If you didn't get more traffic from it - either you have very few pages or you didn't bother to register your sitemap with Yahoo (siteexplorer) and google (webmaster tools)

dkruglyak’s picture

dkruglyak commented

I have >25K nodes and registered the sitemap just fine. But no evidence of traffic improvement.

If you have any objective way to measure the impact let me know.