Keka icon indicating copy to clipboard operation
Keka copied to clipboard

[REQ] ability to configure temporary folder location

Open ahrib opened this issue 1 year ago • 1 comments

Is your feature request related to a problem? Please describe

During decompression, Keka currently creates the temporary file/folder in the same location as the destination.

When extracting a large file to a slow media destination (e.g. a USB drive) the end-to-end extraction process is very slow as :

  1. Keka extracts file to a temporary directory on the destination location
  2. copies temporary directory contents to destination location

For slow media such as USB drives, this means that data is copied twice - making things take a very long time.

Describe the solution you'd like

An option to configure the temporary file location e.g. options such as Same as destination (default), /tmp, etc)

Describe alternatives you've considered

Manual workaround when wanting to extract a compressed file that exists on a USB

  1. extract file on local HDD
  2. copy extracted contents to USB

This is faster than extracting a file directly on the USB drive, however involves additional steps.

ahrib avatar Jul 28 '22 07:07 ahrib

@ahrib the current behaviour is for Keka to do the extraction is:

  • Extract it near the destination with a .kextraction package
  • Rename or move the contents of that package

Note the "temporary" directory is near the final destination. At least on HFS+ and APFS formats, moving a folder is nearly immediate, so this should be the quickest way.

It is true that the extraction itself may be slower in a slow USB drive compared to an internal or fastest disk, and maybe this is your perception, not renaming/moving the .kextraction but the extraction process itself.

Anyway, this might be a nice addition for experienced users.

aonez avatar Aug 02 '22 09:08 aonez