Ok so the question is how big the images are and your approach. What benefit do you see from running multiple threads ?
If you're connecting to one single source and the connection is quick it might just be quicker to pull them down sequentially. Pull them down to local storage then go through and process them. Given that image resizing is cpu intensive and that running multiple threads in itself has some cpu overhead why not run both in a single thread ? A On 9 March 2012 10:12, David Mulder <[email protected]> wrote: > Ok, I don't have much experience with cfthreads, but just a quick > question. In ACF it's possible to limit the number of simultaneous > cfthreads to for example 10, meaning that any threads spawned after that > have to wait till one of the previous threads have completed. Not even sure > that's the best solution to my problem (need to get (http) and resize > 1000's of images as quick as possible). > David > > -- > online documentation: http://openbd.org/manual/ > google+ hints/tips: > https://plus.google.com/**115990347459711259462<https://plus.google.com/115990347459711259462> > > http://groups.google.com/**group/openbd?hl=en<http://groups.google.com/group/openbd?hl=en> > -- Alex Skinner Managing Director Pixl8 Interactive Tel: +448452600726 Email: [email protected] Web: pixl8.co.uk -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en
