Image Processing Resources

I would like to know what limits the number of photos that can be processed in a job. I have just completed a site survey that resulted in 403 vertical, orbital, and ground-based shots and I’m curious to know what I can do to ensure it goes through ok. Is all the processing done locally or some at the ‘Node’, wherever that is? I guess I will know in a significant number of hours :slightly_smiling_face:

I’m using a Mac Mini with M1chip and 16GB ram. I think it’s Meshroom that allows you to allocate varying numbers of CPU Cores and amounts of RAM to its working so I wondered if the same can be done with WebODM.



WebODM should take everything allocated to it via Docker.

You can tune Docker here:

Unless you choose Lightning or Auto (with Lightning signed in), your node-odm-1 is local to that machine.

16GB will likely be a bit tight for 403 images, depending upon size and processing parameters.

Thanks. Does the Lightening Network mean that processing can be done remotely if one thinks there are two few resources on ones local machine? If so am I free to use that?

1 Like

Yes, our hosted Cloud processing solution:

It is not a free resource, no, as the hosting and running of the hardware is expensive. However, I think we have a wide enough variety of plans and service levels that it should suit most folks:

1 Like

Ok I’ll look into that. Can I subscribe short term for say 1month to deal with a large job?

Also, I have set my resource allocation up to 15GB (out of 16) as my first attempt failed for lack of ‘something’. Do I need to reset this back to say 4Gb or only if I plan to run apps at the same time? It doesn’t hold those resources in some way when it’s not running?


1 Like

Sure. You can also do Pay-As-You-Go. Check out the Pricing page I linked above.

I generally do not recommend leaving less than 4GB for the HOST OS, so I would be cautious using more than 12GB.

It will allocate a certain amount for the linux kernel and environment when Docker starts (2GB or so is pretty typical) and it should release RAM as it is released by Docker. That being said, it may not release it immediately.

1 Like

Thanks for all that.

I’ve looked at the various plans and am confused by one thing. One one page it says there’s a limit of 337 images, that can be increased (see first grab)

but on the PAYG option it’s 1000/map.

So if I have my 150 intro credits and buy say 100 more, I can still only upload 337 images maximum in a job?

The PAYG option is basically what I’m on now, I presume, where I buy credits as required and yet the option to ‘increase limit’ of the pic upload number just takes me to the PAYG page so I’m stuck in a loop it seems.

I’m sure there’s a simple answer.

1 Like

Nope, your image limit is currently 337 images since your credits only allow you that many images.

Your Service Plan limit is up to 1,000 images per Task, with 30 concurrent Tasks, provided you have sufficient Credits for that.

1 Like

Does the 3000 image limit only apply to plans? That doesn’t seem to be the limit when using the cost calculator

1 Like

I believe the logic behind the calculator is that you can buy as many credits as you want at once, but that doesn’t mean that you can use all of them in one go.

The Service limits are as stated on the Pricing page in regards to maximum images per Task.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.