Understanding Intelligent Caching Engine in Translator Plugin Pro / Gold 5.0了解智能缓存引擎在翻译插件亲/金5.0

We have designed a new caching engine for Translator Plugin Pro 5.0 & Gold 1.0.我们设计了一个新的缓存引擎为翻译插件亲5.0 ＆ 1.0黄金。 Previously we used WordPress’ Object Caching Engine (bundled with WordPress) which doesn’t work so well in resource constrained sites.以前我们使用WordPress所'的对象缓存引擎（捆绑在WordPress ）不工作这么好，在资源约束的网站。 Also it doesn’t serve our need to have semi-permanent cache for translated pages and provide infrastructure for Translator Pro & Gold moving forward.此外，它没有服务，我们需要有半永久性的快取记忆体为翻译的网页并提供基础设施，翻译亲＆黄金向前迈进。 Our primary design objectives in designing the new caching engine are as follows:我们的主要设计目标在设计新的缓存引擎分别如下：

Translation speedup is the primary goal of any caching effort but there is more. 翻译是加速的首要目标，任何缓存的努力，但还有更多的。 Translating a page requires us to submit the content, after pre-processing, to a translation engine like Google, who then sends us the translated version of the page.翻译网页，要求我们提交的内容后，前处理，一个翻译引擎，像Google ，谁，然后发送我们的翻译版本的网页。 The content is then post-processed and delivered to the client / requester.内容是，然后后处理并传送到用户端/请求者。 This process involves database queries and network traffic, each of which can add up if your site becomes / is popular.这一过程涉及数据库查询和网络流量，其中每个最多可新增如果您的网站成为/是受欢迎。 The goal of caching is not only significantly speedup delivery of translated pages but also to reduce network traffic and database queries.目标缓存不仅是显着加速交付翻译的页面，而且，以减少网络流量和数据库查询。

Availability of service is a key goal. 提供服务是一个关键目标。 Frequent queries to translation engines can cause overload of their services and they in turn can disable your site for a time period or more, which is clearly undesirable.频繁的查询翻译引擎，可导致超负荷他们的服务和他们反过来又可以禁用您的网站为一个时间段或更长时间，这显然是不可取的。 So not only do we need to speedup translation on your site we also need to keep the translation engines happy by managing their load within their acceptable limits.因此，我们不仅需要翻译，以加速在您的网站上我们还需要继续翻译引擎，快乐由管理其负载在其可接受的限度。 We have done extensive tests to understand and satisfy the limits of each translation engines we use.我们已经做了广泛的测试，以了解和满足的界限，每个翻译引擎，我们使用。 We also provide automatic failover support so if one engine fails we move over transparently to another and so on till we are able to satisfy the request or run out of engines (rarely).我们还提供自动故障转移支持，所以如果一个引擎失败，我们提出以上的透明到另一个等，直至我们能够满足要求或失控引擎（很少） 。 We have as much provided 4 translation engines for redundancy.我们拥有尽可能多的提供4翻译引擎冗余。 It is possible that they may change their limits down the road which is why we have made the engine very much configurable from the options panel.是有可能的，他们可能会改变其限制下来，道这就是为什么我们已取得的引擎十分配置的选项面板。

Intelligent caching makes caching more relevant and effective. 智能缓存缓存，使更多的相关和有效的。 In WordPress the traditional model of caching is as used in wp-cache 2 plugin.在WordPress的传统模式缓存中使用的可湿性粉剂缓存2插件。 It invalidates the cache on first sign of change and creates it from scratch again.它无效高速缓存的第一个迹象的变化和创建它从头开始。 It is very inefficient and ineffective for sites with frequent changes and /or frequent comments.这是非常低效和无效的网站，与频繁的变化和/或频繁的评论。 Each new post / updated post / new comment / updated comment etc. will invalidate the cache and start all over again.每一个新的职位/更新后/新评论/更新评论等会作废缓存和重新开始。 It is surely an overkill.它无疑是矫枉过正。 Most of the posts do not change at all when a new post is created or even modified.大部分的职位不改变在所有时，一个新职位，是创造，甚至修改。 We developed various ways for optimizing this scenario.我们开发了各种方式优化这种情况。 The primary objective is to ensure that translated pages are available for all requested content, either by translation (see availability issue above) or from cache, even if the translated page is not always from the latest revision.主要的目的是要确保翻译的页面均适用于所有要求的内容，无论是由翻译（见供货的问题，以上）或从缓存中，即使翻译网页并非总是从最新的修订。 Certain pages like index pages are prioritized for faster refresh.某些网页一样，指数的网页的优先次序为更快的刷新。 The cache is continuously refreshed in the background.高速缓存是在不断刷新的背景。 Our intelligent caching engine achieves over 90% cache hits on average as you can see from the sidebar of this blog.我们的智能缓存引擎达到90 ％以上的高速缓存的点击次数平均为您可以看到从侧栏此博客的。 There are other technologies in place to ensure higher priority is given for humans than for robots / spiders etc.还有其他的技术就绪，以确保较高的优先考虑的是为人类比机器人/蜘蛛等。

Manual Control is provided to individually delete the translated pages from cache or to delete the whole cache (not recommended). 手动控制是提供给单独删除翻译的页面从高速缓存或删除整个快取记忆体（不推荐） 。

The cached pages are compressed in database to minimize space requirements.缓存的页面压缩在数据库中，以尽量减少空间的需求。 However since you will have a maximum of 14 times (you can reduce the number by reducing the number of translations you provide) the amount of content, compressed for space reduction, as the original number of pages you need to have space allocated for the database to hold it.但由于你将有最多14倍（您可以人数减少，减少的数目翻译您所提供的）的数额内容，压缩空间减少，由于原来的页面数量，您需要有空间分配给数据库举行。 If you have limited space for the database then you should either switch hosting provider (I recommend如果您有空间有限，数据库，那么你应该可以开关的托管服务提供商（我建议 WestHost westhost ) or you should reduce the number of translations your provide. ）或你应该减少的数目翻译您提供。