batch add kills machine

[pt]

Hey, I apologize if this has been covered before.  I have an older linux machine and have started uploading large files from my canon 20d (~3.5mb a piece).  My gripe is that when I add more than about 10 pictures at a time my machine spawns enough processes converting images in parallel that the machine dies a horrible swap death and must be rebooted.  This is particularly annoying when your machine is remote.  And when the machine doesn't die it becomes very slow which as forced me to add pictures in off hours (also very annoying).

Looking at the source it seems the only way to get around this is to add a smaller number of files at a time.  It seems like it would be much more reasonable to have addpic.php consider other processes and wait a bit if it notices that there are already one (or a user configurable value) conversions in progress.

I am wondering if there are plans to fix this?  It makes no sense to me that coppermine would spawn so many processes at once when it doesn't get the job done any faster than if it were to perform these operations serially, and I can't imagine that I'm the only one who has had this problem. 

Thanks in advance for any help you can provide.

[Tranz]

Are you using Imagemagick? I have a poor memory but I think that's the one that runs processes in parallel and thus causes resource issues. Try GD2 if you are not already using it.

[dhruvb14]

i too have the same problem using either GD2 or Imagemagick. With gd it cause all my other apache pages to stop loading and using imagemagick cause pages still to load except a 1.5kb index takes 2 minutes to load using the INTRANET not internet.