On Thu Jan 11 17:18:41 2024 +0000, Henri Verbeet wrote:
It would be platform specific, so we'd need some codepath for Unix too.
Right, the idea in such a case would be to use one API on Windows and something else on Linux, although that probably comes with its own set of pitfalls. In any case, having SQLite shipped with Windows certainly makes it a lot more feasible as a potential option.
This is mostly a note for myself for future reference: One quality aspect of the serialization backend is how fast the cache file is loaded into memory. I fed the a somewhat populated cache from Diablo 2 resurrected to the tests/d3d12.cross64.exe, which creates and destroys devices a lot. My simple reader did rather poorly - it increased the test runtime from ~25 to ~55 seconds with the code that actually creates the pipelines disabled.
I didn't implement nor test any alternative backends yet :-)