Question

I have a filter that I use for lang support in my webapp. But when I publish it to GAE it keeps telling me that it the usage of CPU is to high.

I think I located the problem to my filters I use for support. I use this in my templates:

<h1>{{ "collection.header"|translate:lang }}</h1>

The filter code looks like this:

import re
from google.appengine.ext import webapp
from util import dictionary

register = webapp.template.create_template_register()

def translate(key, lang):
    d = dictionary.GetDictionaryKey(lang, key)
    if d == False:
        return "no key for " + key
    else: 
        return d.value

register.filter(translate)

I’m to new to Python to see what’s wrong with it. Or is the the entire wrong approach?

..fredrik

---

Little more about what I’m trying to do: I’m trying to find away to handle language support. A user needs to be able to update text elements via an admin page. As of now I have all text elements stored in a db.model. And use a filter to get the right key based on language.

After a lot of testing I still can’t get to work well enough. When published I still get error messages in the logs about to much CPU usage. A typical page has about 30-50 text elements. And according to the logs it uses about 1500ms (900ms API) for each page load. I’m starting to think this might not be the best approach?

I’ve tried using both memcache and indexes to get around the CPU usage. It helps a little. Should one use memcache and manually added indexes?

This is how my filter looks like:

import re
from google.appengine.ext import webapp
from google.appengine.api import memcache

from util import dictionary

register = webapp.template.create_template_register()

def translate(key, lang):
    re = "no key for " + key

    data = memcache.get("dictionary" + lang)

    if data is None:
        data = dictionary.GetDictionaryKey(lang)
        memcache.add("dictionary" + lang, data, 60)

    if key in data:
        return data[key]
    else:   
        return "no key for " + key


register.filter(translate)

And util.dictionary looks like this:

from google.appengine.ext import db

class DictionaryEntries(db.Model):
    lang = db.StringProperty()
    dkey = db.StringProperty()
    value = db.TextProperty()
    params = db.StringProperty()

    @property
    def itemid(self):
        return self.key().id()

def GetDictionaryKey(lang):
    entries = DictionaryEntries.all().filter("lang = ", lang)
    if entries.count() > 0:
        langObj = {}
        for entry in entries:
            langObj[entry.dkey] = entry.value

        return langObj 
    else:
        return False

Answer 1

Have you considered switching to standard gettext methods? Gettext is a widely spread approach for internationalization and very well embedded in the Python (and the Django) world.

Some links:

• Python’s gettext module

• Django’s support for gettext with special attention to unicode

• PoEdit, an editor for .po-files produced by pygettext

Your template would then look like this:

{% load i18n %}
<h1>{% trans "Header of my Collection" %}</h1>

The files for translations can be generated by manage.py:

manage.py makemessages -l fr

for generating french (fr) messages, for example.

Gettext is quite performant, so I doubt that you will experience a significant slow-down with this approach compared to your storage of the translation table in memcache. And what’s more, it let’s you work with “real” messages instead of abstract dictionary keys, which is, at least in my experience, ways better, if you have to read and understand the code (or if you have to find and change a certain message).