Is there an equivalent UMD cache for ISOs?

A bit of a strange question this one but I've noticed running a couple of games from an ISO/CSO produces worse performance than running the same game from a UMD. I'm wondering if the issue is because the firmware does not utilise the cache when an iso/cso is being used.

For example, Outrun C2C becomes very slow as each section is loaded but is a lot smoother running from UMD. This can be alleviated a lot when running from an iso/cso by changing the game clock speed to 333MHz from the VSH menu.

Similarly, God of War really slows down as sections are loaded. Changing the clock speed doesn't help much (I think GOW uses the full clock speed anyway).

Having said that, Wipeout Pulse runs smoother from ISO/CSO than UMD - but that doesn't have the same in-game mass loading that Outrun and GOW have.

I'm guessing that the issue is because the UMD cache that would be used for a UMD isn't used for games loaded from an ISO.

Is there a patch or a setting that enables the cache?

Or, am I on the wrong path and it's something else?

Its something else

Any clues as to what?

Solved it.

The stuttering occurs when cso files are used instead of iso.

GOW and Outrun play perfectly from iso files.

Yah i prefer to use full ISO's because they run fluently and work better, at the expense of size.

another main reason is the memorystick. Different sizes and brands run faster/slower

ex.

4gb sony = slow
32mb-2gb sony = faster
4gb sandisk = faster
32mb-2gb sandisk fastes

Also, UMDs, ISOs, CSOs, and everything else all use the same RAM.

another main reason is the memorystick. Different sizes and brands run faster/slower

ex.

4gb sony = slow
32mb-2gb sony = faster
4gb sandisk = faster
32mb-2gb sandisk fastes

I've found that Sandisk run much better than Sony, especially for homebrew. I've never actually been able to tell speed difference in a 2gb sandisk and a 4gb sandisk, but i do think that Sony's newer Memory sticks are more up to par

I have an 8GB Sandisk (non gaming type) but using cso images was the problem for me.