What is your setting for "Maximum number of objects to alias in a bulk update: "?

greggles's picture
I left it at the default 50
27% (3 votes)
Between 51 and 250
27% (3 votes)
Between 251 and 500
18% (2 votes)
Between 501 and 1000
18% (2 votes)
Somewhere over 1000
9% (1 vote)
Total votes: 11
Groups:
Login to post comments

purpose of the poll...

greggles's picture
greggles - Fri, 2008-09-19 02:45

I think that we should increase the number, but I'd like to get a sense of what works for people.

I think that we should choose a number that works well on the typical overloaded shared host - so if you have a dedicated server or VPS then either don't answer or answer from the perspective of a site that you have on shared hosting.

Thanks!


I think this should be a

earnie's picture
earnie - Fri, 2008-09-19 12:46

I think this should be a percentage of the cron run with a maximum number in a for the LIMIT of the select and a maximum number of select statements. To answer your question I've used 500 on initial load and decrease it later to 100.


990

wishstik - Fri, 2008-09-19 10:47

990 on shared hosting (site5) which seems to work just fine, though you may get a blank screen occasionally. There's just too much content!


What if I already have a massive amount of content?

franckmercado - Wed, 2009-09-02 22:06

In this case I already have taxonomy terms added to Drupal database and I want to apply "Bulk update".

How can I apply bulk update to all of the terms without having Drupal crashed? Im in a local Vaio laptop with 2ghz Core Duo and LAMP configured properly.

Note: When I apply Bulk update and I put a number like 4000 for the "Maximum number of objects to alias in a bulk update" then Drupal crashes and adds the aliases only to some terms.