Recent Topics
-
PowerArchiver and PACL for macOS
Tech Support3 -
UNSOLVED No Updates Shown
Tech Support3 -
UNSOLVED File Browser: Operations don't trigger UAC
Tech Support7 -
Fast Ring: PowerArchiver 2019 19.00.51/54/57/58/59
Tech Support24 -
SOLVED Problem: Backspace navigation in Explorer mode
Tech Support3 -
UNSOLVED Smart AI: Preferences not intuitive
Tech Support13 -
SOLVED Find file in archive.
Wishlist9 -
UNSOLVED PA 20.00.02 not executing .exe files from archive
Tech Support10 -
PACL 9.0 Beta 2
Tech Support24 -
UNSOLVED Minor UI question
Tech Support7 -
SOLVED Slow Download
General Chat3 -
SOLVED ZIPX-jpeg-compression
Tech Support2 -
SOLVED PA standard 2019 can not create PA-archives
Tech Support2 -
UNSOLVED The PACL does not extract files from the self-extracting archive
Tech Support3 -
UNSOLVED PA 19.00.57 - Drawing issue on file type collumn
Tech Support2 -
UNSOLVED PA 19.00.57 crashes Firefox 69.0.1 in module pashlext64.dll | UserCallWinProcCheckWow
Tech Support18 -
UNSOLVED Include all PowerArchive Toolbox features in the offline installer
Tech Support3 -
UNSOLVED PA 2019 explorer preview window always blank
Tech Support3 -
UNSOLVED Encrypt files inside archive that has already been created [.zipx]
Wishlist5
Behavior change request.
-
If I extract a file from powerarchiver to a folder, power archiver extracts the file to a temp directory, then copies the file to the location, then deletes the temp copy. When you are working with large files this presents a huge unessary slowdown and a lot of wasted disc space.
WinRAR handles this better by extracting to a temp directory, then MOVING the file to the correct location instead of copying it. In WindowsXP this is just a change in the File Allocation Table or NTFS equivilant, saying that the file is now located in X directory, which is very fast, no need to create 2 copies of the file then delete one of them.
If you are extracting a 4gb file you only need 4gb of space, not 8gb like currently required by powerarchiver for the same operation.
Make sense?
-
guess it does.
but let’s hear from dev’s…
-
I believe that if you use “write directly into zip” option, you can make it write directly into zip file, w/o using temp which then speeds everything up.
If you want to make that pernament setting, you can set it up at Options>Config>Misc, and it should work with all formats!
Does that work as intended?
thanks,
-
SPWolf,
I couldn’t find the setting you mentioned, where is it and what is it called?
Thanks!
-
It should be under Speed options> Use current folder as temp. That should work for compression only of course.
thanks,
-
Well, that helps some, but since it doesn’t affect decompression, it isn’t really what I was asking/requesting. My intention in starting this thread was to make development aware of a very small change that would improve performance proportional to the size of the files.
Thanks.
-
Great tip! I would like this feature as soon as possible