RadeonSI Quietly Landed A Shader Cache As A Last Feature For Mesa 11.2

[plonoma]

Do you mean latency on a rotational disk, not SSD? I have my home directory (and consequently the shader caches, such as ~/.AMD/GLCache) on an SSD.

Since the moment I bought an SSD, latency isn't an issue in any application I am running - the CPU speed is now the limiting factor.

Or can latency of the shader cache be an issue even on an SSD?

Not everybody has an SSD. Many people still use rotational disk(s).

[geearf]

Not everybody has an SSD. Many people still use rotational disk(s).

You could use a tmp drive and sync it back to HDD on shutdown/restart. (Of course that demands enough RAM, even with a compress FS...)

[pal666]

Not everybody has an SSD. Many people still use rotational disk(s).

then they will preload shaders in page cache

[duby229]

You could use a tmp drive and sync it back to HDD on shutdown/restart. (Of course that demands enough RAM, even with a compress FS...)

That's pretty much the only way to get playable framerates on wine with The Old Republic online. It uses a disk cache that needs to be on a tmp drive. (which brings it from a 6GB minimum requirement to a 12GB minimum requirement)

[smitty3268]

That's pretty much the only way to get playable framerates on wine with The Old Republic online. It uses a disk cache that needs to be on a tmp drive. (which brings it from a 6GB minimum requirement to a 12GB minimum requirement)

The OSS drivers will almost certainly keep around an environment variable letting you disable the cache whenever you want, for debugging purposes if nothing else.

There's one already for this radeonsi caching.

[duby229]

The OSS drivers will almost certainly keep around an environment variable letting you disable the cache whenever you want, for debugging purposes if nothing else.

There's one already for this radeonsi caching.

Cool, that means benchmarking options. That is one of the best things the OSS devs offer imo. It means we can all see how the performance turns out.

[liam]

Do you mean latency on a rotational disk, not SSD? I have my home directory (and consequently the shader caches, such as ~/.AMD/GLCache) on an SSD.

Since the moment I bought an SSD, latency isn't an issue in any application I am running - the CPU speed is now the limiting factor.

Or can latency of the shader cache be an issue even on an SSD?

Seek times aree STILL an issue with ssds. If it wasn't, you wouldn't see bandwidth plummet when performing random access. Even in the best cases, ssds still have a latency x1000 higher than memory. In fact, they are closer to the access times of a hard disk than to memory.
Hopefully xpoint will remedy this, somewhat.

[geearf]

That's pretty much the only way to get playable framerates on wine with The Old Republic online. It uses a disk cache that needs to be on a tmp drive. (which brings it from a 6GB minimum requirement to a 12GB minimum requirement)

12Gb starts to get quite steep (I have 16Gb, but I feel newer games will probably ask even more).
As the follower poster said, it'd be great to be able to configure the path of the cache (once it gets pushed to a partition), maybe on a per process basis.

[plonoma]

Cool, that means benchmarking options. That is one of the best things the OSS devs offer imo. It means we can all see how the performance turns out.

Environment variables are a bad way to specify such options.
Instead of an environment variable, a per-application setting and a per graphics driver setting would be better for dealing with such cache behaviour.
(+ a way to determine, set which GPU's are used in benchmarks)
It's easier to work with for benchmarking applications.

[duby229]

12Gb starts to get quite steep (I have 16Gb, but I feel newer games will probably ask even more).
As the follower poster said, it'd be great to be able to configure the path of the cache (once it gets pushed to a partition), maybe on a per process basis.

I'm pretty sure the disk cache that eventually gets developed for the OSS drivers will be a different type of beast from the disk cache that the Old Republic online uses. I just gave that as an example of a methodology that hurts performance. I just figured if the OSS devs are aware of one example of a disk cache that doesn't work well at all, then at least that would be in their minds as they implement the disk cache for the OSS drivers.