hugin-devs team mailing list archive

[Christoph Spiel <cspiel@xxxxxxxxxx>]

1. The option "-m" only affects the image cache.
If Enblend/Enfuse are built w/o it they automatically /
"naturally" use all available (virtual) memory.

2. You can get a more dynamic adjustment of the
image cache size by tapping the free(1) or vmstat(1).
tools or directly consulting /proc/meminfo.  Feed this
info to the "-m" option.

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/822690

Title:
  automatic detection/use of memory.

Status in Enblend:
  New

Bug description:
  background:

  the default for the -m option is 1024Mb. This means that you'll need
  about 1Gb of swap if your machines has less than 1G of RAM. Fine. When
  you have 1G of RAM, you'll be fine. You'll waste some RAM if you have
  2G, but if you have 4, 8 or 16Gb, enblend will run in a tiny part of
  RAM and leave the rest unused.

  Wishlist:
  Enblend should, when RAM >> 1G, auto-adjust the -m parameter to say 0.75 * RAMSIZE. (limited to 2048 if sizeof (long) == 4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/822690/+subscriptions