[MINC-development] max_buffer_size_in_kb

Alex Zijdenbos zijdenbos at gmail.com
Thu Aug 11 08:33:39 EDT 2011


I'm all for this. I recently had a case for which processing time went
from around 7 hrs to 10 mins or so by changing the buffer size. An ENV
var approach would be good, but regardless I think we should change
the default as well, it seems rather outdated.

-- A

On Thu, Aug 11, 2011 at 4:42 AM,  <jcupitt at gmail.com> wrote:
> On 11 August 2011 08:03, Andrew Janke <a.janke at gmail.com> wrote:
>> Would anyone be against me upping the default limit (4MB in most tools)?
>>
>> Perhaps we should take an ENV var approach?
>
> Sounds good.
>
> For what it's worth, most libraries seem to use both env vars and
> command-line switches, so you could have:
>
> $ minc-process file.mnc
>
> will use the default buffer size
>
> $ MINC_BUFFER=64m minc-process file.mnc
>
> will use a 64mb buffer and
>
> $ MINC_BUFFER=64m minc-process --minc-buffer=8m file.mnc
>
> will use a 8mb buffer (command-line switches always override env
> vars). The idea is that the env var sets the default, the switch sets
> the value for this invocation.
>
> John
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>
>


More information about the MINC-development mailing list