I know this sounds very old-school, but a temp file on your SAN would be easy and cheap.
Loading a 300M file at the start of each run is trivial compared to consuming 300M of cache all the time.
And if you can recreate it from the database keys, it would be wise to write and test that part and make it automatic that if the temp file was unavailable, the info would be mined from the keys and recreated.
发布评论
评论（1）
我知道这听起来很老派，但是 SAN 上的临时文件会很简单而且便宜。
与一直消耗 300M 的缓存相比，在每次运行开始时加载 300M 的文件是微不足道的。
如果您可以从数据库密钥重新创建它，那么明智的做法是编写和测试该部分并使其自动，如果临时文件不可用，将从密钥中挖掘信息并重新创建。
I know this sounds very old-school, but a temp file on your SAN would be easy and cheap.
Loading a 300M file at the start of each run is trivial compared to consuming 300M of cache all the time.
And if you can recreate it from the database keys, it would be wise to write and test that part and make it automatic that if the temp file was unavailable, the info would be mined from the keys and recreated.