New - ISO compression - help testing
#81
It looks like you are only saving a few hundred MB per iso. Unless you have a massive number of games, this seems like it may not be a great use of time (talking about compressing isos, not the support in PCSX2). If the average iso is 4 GB and each compressed saves 200 MB, then it would take you 20 isos of compression to store one more iso on your pc. Am I just not getting it?
Intel Core i5-8600K @ 4.5 GHz
GeForce GTX 1080 SC2 Stock
ASRock Z370 Taichi LGA 1151 mobo
CORSAIR Vengeance LPX 16GB 2400 DDR4 RAM
SAMSUNG 970 EVO M.2 2280 500GB PCIe SSD
Indigo Xtreme Thermal Interface Material
Phanteks Enthoo Pro ES614P Black Steel Case
EVGA SuperNOVA 750 G2 220-G2-0750-XR PSU
Windows 10 64-bit
Reply

Sponsored links

#82
The amount of compression you get is very dependent on the game. For example ICO compressed down to 701MB, and Kingdom Hearts down to 2.27GB.
[Image: pNm13X9.gif]
Windows 10 Pro x64 Version 1909 | AMD Ryzen 5 5600X | GIGABYTE AORUS GeForce GTX 1080 Ti | Crucial 16GB (2x8GB) DDR4 3600 RAM | Samsung 850 EVO 500 GB SSD | WD Red Plus 8TB

CPU Intensive Games
GPU Intensive Games
Games that don't need a strong CPU
Reply
#83
Ah! Well that makes sense. I went on the assumption of a few data points I saw in the thread. Shame on me for assuming Tongue
Intel Core i5-8600K @ 4.5 GHz
GeForce GTX 1080 SC2 Stock
ASRock Z370 Taichi LGA 1151 mobo
CORSAIR Vengeance LPX 16GB 2400 DDR4 RAM
SAMSUNG 970 EVO M.2 2280 500GB PCIe SSD
Indigo Xtreme Thermal Interface Material
Phanteks Enthoo Pro ES614P Black Steel Case
EVGA SuperNOVA 750 G2 220-G2-0750-XR PSU
Windows 10 64-bit
Reply
#84
(02-06-2015, 11:57 PM)karasuhebi Wrote: The 11 option doesn't use zlib, it uses zopfli which is MUCH slower (100x slower, according to their own site). Just for ***** and giggles I tried it. I let it run for 35 minutes (since 7-Zip on 'Ultra' takes ~30 minutes) and then I canceled out of it. It had only processed about 1.5 of the FFX.iso when I stopped it. So yeah...SUPER slow.

Thank you. So it's practically useless.
Reply
#85
Yeah, pretty much. I should clarify though, it had processed 1.5 GB of the FFX.iso. Forgot the 'GB' XD
[Image: pNm13X9.gif]
Windows 10 Pro x64 Version 1909 | AMD Ryzen 5 5600X | GIGABYTE AORUS GeForce GTX 1080 Ti | Crucial 16GB (2x8GB) DDR4 3600 RAM | Samsung 850 EVO 500 GB SSD | WD Red Plus 8TB

CPU Intensive Games
GPU Intensive Games
Games that don't need a strong CPU
Reply
#86
(01-09-2015, 12:33 PM)avih Wrote: Should be fixed - https://github.com/PCSX2/pcsx2/commit/7b7a977

Please test and let me know if it works.

Also, if anyone with Linux could also test, please post a comment too. Thanks.

Still not fixed. I decided to rename my 'Okami (U).iso.gz' to 'Ōkami (U).iso.gz' (I also tried renaming the .iso contained inside but that didn't seem to work) and now PCSX2 crashes as soon as I try to boot the game. I'd like to add that I deleted the old .pindex.tmp file before trying to boot the game. Using the latest development version (v1.3.1 #9).

I tried it on a previous build I had laying around (v.1.2.1, #677) and instead of auto crashing, I get this:
[Image: HJrezCa.png]
[Image: pNm13X9.gif]
Windows 10 Pro x64 Version 1909 | AMD Ryzen 5 5600X | GIGABYTE AORUS GeForce GTX 1080 Ti | Crucial 16GB (2x8GB) DDR4 3600 RAM | Samsung 850 EVO 500 GB SSD | WD Red Plus 8TB

CPU Intensive Games
GPU Intensive Games
Games that don't need a strong CPU
Reply
#87
Could you please try exactly the same thing with this? http://buildbot.orphis.net/pcsx2/index.php?m=get&rev=v1.2.1-855-g7b7a977&platform=windows-x86

This is the build from 2015-01-09 11:07:03 which is the build which should have supposedly fixed it (it did fix it on my system). If this build works OK but the latest one doesn't, then maybe it somehow got broken along the way.

Let me know the results. Thanks.
Reply
#88
Weird, but apparently my earlier fix for non-english file names didn't actually work on some non-english file names. It's weird since I'm pretty sure I tested it and it worked fine, but now I tested it again and it crashes again.

Anyway, I pushed another fix: https://github.com/PCSX2/pcsx2/commit/f2657ae which should appear shortly on at the automatic build-bot pages. Hopefully this time it'll work better.

I tested it with several non-english file names, including "Ōkami (U).iso.gz" which was crashing before this last fix, but works well with the last fix.

Please test and let me know. Thanks.
Reply
#89
It's working for me just fine now Smile
[Image: pNm13X9.gif]
Windows 10 Pro x64 Version 1909 | AMD Ryzen 5 5600X | GIGABYTE AORUS GeForce GTX 1080 Ti | Crucial 16GB (2x8GB) DDR4 3600 RAM | Samsung 850 EVO 500 GB SSD | WD Red Plus 8TB

CPU Intensive Games
GPU Intensive Games
Games that don't need a strong CPU
Reply
#90
Added a system which asks the OS (windows only) to prefetch the next chunk from disk after the current extract finishes. This should help with sequential access of fragmented files without any noticeable negative impact.

Since this prefetch is asynchronous, it doesn't slow down PCSX2.

This should help on cases where the disk chunk is accessed the first time before the OS had a chance cache it, e.g. when running a game which wasn't running for a while, but also on other cases where the OS just dumped its cache since the last time the game was played.

https://github.com/PCSX2/pcsx2/commit/6b48784
Reply




Users browsing this thread: 1 Guest(s)