Time to process fast orthophoto

I am making comparisons of ODM (win) and webodm + dokers in ubuntu with a computer with little 4GB ram and I observe that ODM (win) is able to process jobs that webodm does not support, 81 images in my case, with the run instruction (path access to images), it takes one night, but when using the command run fast orthophoto (path to images) the equipment can take days to process the work, using the hard disk, what instructions should be put to do it more quickly, in fast orthophoto mode?

1 Like

Ricardo, it looks like it is taking days since it is swapping/paging out to your slow hard-drive since there isn’t enough RAM.

If you have a large very fast USB, you can use that for Windows ReadyBoost, or if you have a fast internal SSD, you can force the swap/pagefile there. It will still be slow since flash is orders of magnitude slower than RAM, but it will also be many times faster than swap/paging out to a mechanical disk.

Thanks and congratulations by your new workplace on this forum


Thanks for the support!

Let me know if you try ReadyBoost or adjusting your swap drive!

1 Like

imagen I reformulate the question, as the limiting factors, Liebig law of the minimum, of data processing are the amount of RAM of the equipment, 16-32 gb recommended for ODM and WODM; and the speed of the internet connection, fiber optics, for NODM and CODM.What concatenation of ODM commands can I use to make an orthophoto to optimize the RAM of a 4 GB laptop and a 4G telephone connection; following the pipeline … an example of syntax of several chained commands in odm screen would be very useful for learning … my personal experience gave contradictory results as I mentioned in the post, a fast orthophoto took days and a run path to images only 8 hours

1 Like

That’s a really tough question…

I’m also quite ignorant of the realities of processing with 4GB as I have simply not tried such yet.

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