[fleisher]

Gibt es irgendeine Möglichkeit in den JDownloader 2.0 Winrar einzubinden statt Unzip???????????
Danke und Gruß

[fleisher]

Gibt es irgendeine Möglichkeit in den JDownloader 2.0 Winrar einzubinden statt Unpack200???????????
Danke und Gruß

[raztoki]

The simple answer is no, provided support is via a open source 7zip library and it's integration is linked to that. You could theoretically create a evenscript and port it via cli but without the features of in the inbuilt extractor and its respective settings.

[pspzockerscene]

Nein.
Wir verwenden auch nicht "Unpack200" sondern folgende open source Entpack-Library:
github.com/borisbrodski/sevenzipjbinding

Aus welchem Grund würdest du gerne eine andere Library verwenden?
EDIT

Doppelte Threads zusammengeführt.

[fleisher]

Na aus demselben Grund warum fast alle einen anderen Entpacker einbinden wollen:
weil der so grottenlangsam ist.
nd ich habe schon wirklich alle Tricks und Tipps versucht die hier im Forum angeboten werden aber es hat nicht viel gebracht. So braucht der Jay Downloader für 2 Gigabyte ca 2 Minuten während WinRAR das in einem Zehntel der Zeit schafft, das mag jetzt nicht viel klingen, aber bei einem 80 Gigabyte Download macht sich das deutlich bemerkbar.
Gruß

[pspzockerscene]

Originally Posted by fleisher

Na aus demselben Grund warum fast alle einen anderen Entpacker einbinden wollen:

Wer ist "fast alle"?

Originally Posted by fleisher

weil der so grottenlangsam ist.

Mehr Infos zu deinem System bitte.

Originally Posted by fleisher

nd ich habe schon wirklich alle Tricks und Tipps versucht die hier im Forum angeboten werden aber es hat nicht viel gebracht.

Welche Tipps hast du probiert?

Bitte poste deine Log-ID hier.
Falls dein gemeldetes Problem ein Problem mit einer Webseite ist, die per Plugin unterstützt wird, stelle bitte zusätzlich Testlinks zur Verfügung, mit denen sich dein Problem nachstellen lässt.

Eines vorab:
Die Entpacklibrary ist nicht austauschbar und wir planen auch nicht, diese durch eine andere zu ersetzen.

[fleisher]

Windows 11 Pro
i7 9700k
32 GB RAM
18.09.23 16.28.15 <--> 18.09.23 00.21.00 jdlog://9187311370661/
Gruß

[pspzockerscene]

Welche Tipps hast du bereits probiert?

Ich nehme an du hast eine SSD? Falls ja, welche?

Liefen während deiner Entpack-Tests noch Downloads?

Bitte schau unter Einstellungen -> Profieinstellungen -> Extraction.cpupriority -> Das sollte auf "HIGH" stehen.

[horpscorp]

Jdownloader is about 4x slower than Winrar extracting the same files to the same location. This has been the case for as long as I can remember. Not a dealbreaker by anymeans, but on larger downloads it can be the difference between 1-2 minutes and 4-8 minutes. Not an insignificant amount of time if you're trying to get to watching something. This has been my experience on multiple machines.

[pspzockerscene]

Are you mostly extracting some big- or many small files?

There are settings to play around with that can make extraction in JD faster.
Also the problem is not the library we are using but other factors.

[horpscorp]

mostly movies (50-80gb) split into 30-50 files or so.

[pspzockerscene]

Check your cpupriority setting and adjust your maxbuffersize setting:
https://board.jdownloader.org/showthread.php?t=88690
-> Then check if that helps.

[horpscorp]

CPU was set to high. Changed buffer to 8192 from 500. 0 change.

[raztoki]

This is just me thinking aloud, and disclaimer, I personally haven't used extraction program in decade or more and these are just assumptions on my part.

@horpsorp, & others when you're comparing other programs and speed, are you comparing at similar times and system demands? For instance, are the exaction events happening while downloading or post download? The reason I ask is most people extract while downloading other things within JD, which does create large demand either on SAS/SATA ports or related bottle necks on hardware. And when users are manually extracting is the system is less busy? comparing freeway flowing vs freeway in a traffic jam.

When a user firing off Winrar extraction task, this might be achieving less demand on system? I'm thinking how could this be other than a better algorithm / program (which would be hard to 'fix', other than changing libraries). I'd assume that in this day and age a program like Winrar most likely uses some type of dynamic performance optimisations based on volume size, and compression ratios, where as JD seems to be static?

[pspzockerscene]

Jiaz once also mentioned that Winrar might be using multiple CPU cores for extraction while the lib we are using doesn't though I've never looked into this.

If in doubt, you can always use external tools for extraction.

[raztoki]

yes multiple cores most likely explain that also.

[horpscorp]

Originally Posted by raztoki

This is just me thinking aloud, and disclaimer, I personally haven't used extraction program in decade or more and these are just assumptions on my part.

@horpsorp, & others when you're comparing other programs and speed, are you comparing at similar times and system demands? For instance, are the exaction events happening while downloading or post download? The reason I ask is most people extract while downloading other things within JD, which does create large demand either on SAS/SATA ports or related bottle necks on hardware. And when users are manually extracting is the system is less busy? comparing freeway flowing vs freeway in a traffic jam.

When a user firing off Winrar extraction task, this might be achieving less demand on system? I'm thinking how could this be other than a better algorithm / program (which would be hard to 'fix', other than changing libraries). I'd assume that in this day and age a program like Winrar most likely uses some type of dynamic performance optimisations based on volume size, and compression ratios, where as JD seems to be static?

I extracted the exact same movie archives back-to-back from one SSD to another. First running with Winrar, then with Jdownloader. I've done this exact same thing with every settings change I've tried. Same files being extracted to the same location every time. Nothing else was going on in the background.

[horpscorp]

Originally Posted by pspzockerscene

Jiaz once also mentioned that Winrar might be using multiple CPU cores for extraction while the lib we are using doesn't though I've never looked into this.

If in doubt, you can always use external tools for extraction.

So, just to see, I set core affinity to 1 CPU core for both Jdownloader and Winrar. Winrar took 1min and 20 seconds to extract a 50gb archive of 36 files. Jdownloader took over 5 minutes. This is roughly what I would get without setting any core affinity. Both were showing a single core to be maxed out.

Without affinity set, Winrar would mostly stick to one CPU core, and jdownloader showed a single thread bouncing around to multiple cores. There is more background CPU usage during Winrar extraction due to the throughput of the caching software I use (Primocache) being 4x higher .

Anywho, my conclusion is that something is up with the 7zip plugin. One thought I had was that maybe winrar used AVX and the 7zip plugin didn't, but the package power on my CPU is 30w for both programs. AVX would use more power if it were being used (or maybe both are using it, who knows)

Yeah I can just use winrar for stuff where im waiting to download/extract to watch something. Half the time I forget to turn off auto-extract though, and then the extraction is tough to kill once it's started. This is definitely a nit-picky thing, but who knows, maybe my post might contribute to a fix.

Here is Jdownloader with no affinity set:



Here's winrar with no affinity set:



Here is Jdonloader with affinity set to CPU 1:



And here is Winrar with affinity set to CPU 1:

[pspzockerscene]

Thanks for your detailed feedback.
Unfortunately I can't really help with the extraction topic so you will need to wait for a more detailed answer of another team member.