Cache mtime in memory to avoid stat() calls for url expiry about webassets

[miracle2k]

Yes, that's something I would like to add.

I wonder whether it's necessary to come up with a generic mechanism to cache this kind of data (so something like Django can put it's own cache options on top of it), or whether simply using an in-process memory cache is good enough. Thoughts?

[rslinckx]

I use a simple dict mapping filename to hash token. If you use more than 1 process, then the cache will be duplicated of course. I don't know if this is a problem. Also for file hashing maybe the cache should be pre-computed in a separate file to avoid slowing down incoming requests when the cache is empty..

[statico]

We just ran into something like this. I ended up using our current git revision hash (shortened) as part of the filename. In production I set ASSETS_EXPIRE to None.

[miracle2k]

This is fixed in the version branch.

If auto_build = False, then the version (i.e. timestamp) will be cached in memory for each bundle. If a manifest is used, only one filesystem request is required to read all versions per process/env.

[miracle2k]

The version branch has been merged into master.