Use this singleton rather than instantiating new ExifTool instances
in order to leverage a single running ExifTool process.
As of v3.0, its ExifToolOptions.maxProcs is set to the number of
CPUs on the current system; no more than maxProcs instances of exiftool
will be spawned. You may want to experiment with smaller or larger values
for maxProcs, depending on CPU and disk speed of your system and
performance tradeoffs.
Note that each child process consumes between 10 and 50 MB of RAM. If you
have limited system resources you may want to use a smaller maxProcs
value.
See the source of DefaultExifToolOptions for more details about how
this instance is configured.
Use this singleton rather than instantiating new ExifTool instances in order to leverage a single running ExifTool process.
As of v3.0, its ExifToolOptions.maxProcs is set to the number of CPUs on the current system; no more than
maxProcsinstances ofexiftoolwill be spawned. You may want to experiment with smaller or larger values formaxProcs, depending on CPU and disk speed of your system and performance tradeoffs.Note that each child process consumes between 10 and 50 MB of RAM. If you have limited system resources you may want to use a smaller
maxProcsvalue.See the source of DefaultExifToolOptions for more details about how this instance is configured.