Hi Rick, Best way to go is to test full scale in your
environment; having said that I don't think you should have a
problem using IOS however you would like to. When using IOS I
uploaded large jobs with plenty of extras without issue. There are
a ton of variables... from images, graphics, templates, internet
speed, computer, etc. so I can't really give you a images/job time
frame quote. Also keep in mind, you have control over image sizes
Tommi- Thanks for the info. My real concern was, all other things being equal, will larger original files make for longer upload times. It looks from the KB article that it would not.
I will test myself.
Larger original files take longer to process into the online
thumbnail, but your internet connection is likely going to be the
limiting factor here, and to an extent how fast the server can
receive the images in the firstplace. We're getting around 1.5mb/s
up to the server in LA (we're in san diego for reference). We
usually let an upload get going and then time 20 or so images to
get an average per image upload time, then it's [time per image] X
[number of images] for a fairly conservative estimate.
Also for reference, our larger jobs are 5000 images, and while
it takes awhile to upload it really isn't bad. That, and we're
usually uploading at night or while we're working on other things.
It's not something you need to babysit really.
Thanks for the info. If I'm understanding you correctly, the actual upload of the online thumbnail is not an issue with larger images but computer processing time could be.
Our images usually run 5-7 MB ea. but they're talking about shooting more like 20 MB ea. Since we never print school pics bigger that 11x14, I'm of the opinion that the larger size is overkill. Besides the obvious issues with storage and backup, the longer processing times could be probematic.
I'll have to run some comparison tests.
Further to what's already been stated here I can confirm we most
definitely do not upload the full size image. Sub-sampling takes place
at the workstation where you're running tsIOS. (in fact we don't send
jpg files at all - it's sent as binary data that is stored in the your
web server SQL database. There are no loose files anywhere)
With this in mind a big consideration is also your local network.
Presumably your images are stored on a file server somewhere that your
workstation accesses. So the big jpegs need to retrieved from the
server, to the workstation where they are subsequently sub-sampled
before uploading. Obviously the bigger these files are the slower they
will be to move over your network.
As Tommi mentioned there are many many factors that contribute to
overall upload times.