Hi leszek, when you say that first the data is kept in memory and from time to time persisted to disk, is there a way to trigger that the local development server should save it to disk immediately?
The problem is that we are using a GAE app only locally (no internet access) and have sometimes seen strange save issue, where adding new data supposedly has work and on the next start it is not there anymore. (so that's why I guess that your explanantion could be the reason for that - but I would say that this only happened 10% of the time) Thanks for any help in advance. Dominik On Oct 26, 4:26 am, leszek <leszek.ptokar...@gmail.com> wrote: > The development server contains local implementation of low-level > datastore operations. It is something kept in memory and from time to > time persisted to disk. In production environment (app engine) the low- > level engine is Google's Big Table. So you cannot compare performance > between local and production environment - the underlying technology > is completely different. > The development server is only to make your solution running - to > optimize and orchestrate it you need the app engine (production) > environment. So I think that finding bottlenecks in your application > and some refactoring is necessary if current efficiency is not enough. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
