Any performance impacts of using -api LargeFileSupport=1?

[RhetTbull]

I am the author/maintainer of the https://github.com/RhetTbull/osxphotos tool which exports photos with associated metadata from Apple Photos.  osxphotos will optionally use exiftool to write metadata to the exported files or read metadata from files to use in it's template system (https://github.com/RhetTbull/osxphotos#template-system) for naming exported files.  A user recently pointed out that this fails if the file is > 4GB (which is rare but can happen for video files).  osxphotos calls exiftool from a custom python interface I created for this purpose (maintains a singleton exiftool subprocess for better performance).  The easiest fix for this issue appears to be including -api largefilesupport=1 in the parameters to exiftool.  Is there any performance impact of leaving this enabled all the time?  If so, I may want to check the file size of the photo/video in question and only enable this when needed.

[StarGeek]

Take a look at this thread.

[RhetTbull]

Perfect -- thanks! The tool in question runs only on macOS which appears to support large files in exiftool so I don't see any reason from that thread to not enable this by default.