So if I understand this correctly. If a page has a dynamic part, like a most read sidebar that is constantly changing, it gets cached and never deleted. So over time the cache area has cache files that are obsolete. If you delete the cache files it causes a retranslation which is not desirable for a translated page is much faster than a non translated page. But after 1 year the pages get retranslated regardless.
It seems the solution to the growing number of cache files would be to delete files over 1 year old on a regular basis. Am I understanding this correctly?
I like, recommend and would use your enterprise service as you suggested, but unfortunately I get too much traffic and you effectively priced me out of the service some years back. I have spent a lot of effort accommodating gtranslate pro version over the years and here's what I have learned.
For others to shorten the learning curve. here's what I do. Keep in mind that I have probably over 500,000 translated pages.
1. Processing speed is very important. I myself need 9700+ benchmark speed or better(cpubenchmark.net). A lot of ram doesn't help me near as much as the fast processor.
2. I place the gtranslate directory on an ssd with a symbolic link to it. I have thought about adding the gtranslate directory to a ram disk and then writing the content back to a disk ever so often, but have not yet tried this.
3. I use the free version settings of the gtranslate module on my pages, but with the pro setup in place. Therefore people from search engines use the pro version and direct traffic uses the free version which operates very fast and smoothly. It seems the best of both worlds. This works for me as I am bombarded by search engines and they do the heavy lifting of causing the pages to be translated.
With this setup I almost always have translated page loads under 10 seconds worldwide. Hope this helps.