3 ms·
I just started writing a GAE open-source community tool for rare disease orgs two weeks ago. I thought it was slow, but wrote it off as a limitation inherent to
by chasingsparks 16y ago
I just started writing a GAE open-source community tool for rare disease orgs two weeks ago. I thought it was slow, but wrote it off as a limitation inherent to the Datastore. I moved a lot of things to the Memcache level, mitigating (mostly) the slow queries. That being said, I am glad it was actually a real problem.
I'm also impressed that they are not charging anyone until the problem is solved.
- richardw 16y agoGAE does have some performance surprises even during normal performance periods, so it's good that you're using Memcache etc now. Couple other ideas: Try to minimize read effort as much as possible, so e.g. pre-calculate as much as you can and rather optimize for performance than data cost. Data is cheap, so de-normalise where you need speed. Calc offline, so add a task to calculate something and return immediately to the user.