§ Translator Contents翻译内容

I have been trying hard to update all of our existing customers with the latest version of我一直在努力更新，我们所有的现有客户的最新版本 Translator Plugin Pro翻译插件亲 . 。 It is a hard and time consuming effort (and without any remuneration).这是一个努力和时间消费的努力（和没有任何报酬） 。

There are essentially two challenges to this.有基本上有两种挑战了这一点。 First of all the batch processing script used to create a customized version is doing something very strange.首先，所有批次处理脚本用来创建了定制版的是做一些很奇怪的。 For the first processing it is taking around 1 minute 10 seconds, for each subsequent processing the time is increasing in an arithmetic progression; 30-34 seconds each time.为首次处理，这是考虑周围的1分钟10秒，其后每处理的时间是在增加一个算术级数; 30-34秒，每一次。 So the second client is processed in 1 minute 40 second , the third in 2 minute 25 second and so on.因此，第二是处理客户端在1分40第二，第三次在2分钟二五秒等。 The code looks fine.代码看起来罚款。 I wonder through whether PHP does automatic garbage collection like java.我不知道是否通过的PHP是否自动垃圾收集一样， Java的。 In any case memory isn’t increasing significantly.在任何情况下的记忆是不增加显着。 CPU is heating up but not appreciably. CPU是升温，但并非略微。 I still don’t understand the cause of this delay.我仍然不明白造成这种延误。 Also after one batch is run the subsequent batch picks up from where it ended last time + 30-34 seconds.此外，后一批次运行随后一批拿起从那里结束的最后时间+ 30-34秒。 In some situations the counter resets.在某些情况下，柜台重置。 But I haven’t been able to consistently reproduce it. Any ideas as to what could be causing this?但我尚未能一贯重现。 任何意见，以什么，可能会对身体造成这？
Update: I have found and fixed the problem. 更新：我已发现并修复此问题。 It is related to a third party library we were using for processing the file.这是关系到党的第三图书馆，我们所使用的处理该文件。

The second challenge is customization.第二个挑战是定制。 Several customer have come with small requests of customization down the road which we have done for them, often free.几个客户来与小的要求定制下来的道路，我们所做的对于他们来说，往往是免费的。 However it becomes a royal pain to find out the requests from email search in MS Outlook.然而，成为皇家疼痛摸清请从电子邮件搜索在MS Outlook中。 It is possible, despite my best and laborious effort at accuracy, that I may miss someone’s customization or even sending an update.那是可能的，尽管我最好的辛劳和努力的准确性，我可能会错失别人的个性，甚至派遣一支更新。 So please don’t hesitate to contact me if you do not find your update by wednesday or you think we have missed your existing customization.所以请不要随时与我联系如果您没有找到您的更新或周三，你认为我们错过了您现有的定制。 Please be patient.请耐心等待。 I am trying my best to esnure everyone receives their upgrade.我想我所能， esnure每个人都收到他们的升级。

This update is a wakeup call for full automation.此更新是一种唤醒呼吁全面自动化。 I am already designing a database (inhouse; not exposed to the internet) for storing the customer and order details which we will use to fully automate future upgrades.我已经设计一个数据库（内部;不会暴露到Internet ）用于存储客户和订单明细，我们将使用完全自动化未来的升级。 Also we will need to distribute the upgrade scripts to different machines.我们也将需要分发的升级脚本，以不同的机器。 I will either use Condor as this is ideally suited for it or develop a custom java based distributed batch processing software.我会使用秃鹰，因为这是适合它或建立一个自定义基于Java的分布式一批处理软件。 Any suggestions are welcome.任何建议，是值得欢迎的。 However it is easier said than done considering our tightly packed product development schedule till December 2007.不过，这是说起来容易做起来考虑，我们紧紧地挤满了产品开发的时间表，直至2007年12月。

Update: The final batch of updates have been scheduled for processing. 更新：最后一批更新已排定处理。 I will do a final check tomorrow to see if I missed anyone.我会做最后检查，明天见，如果我错过了任何人。 So if you don’t hear by end of tomorrow, please speak up.因此，如果您没有听到年底明天，请你发言。