Hi Prashant, In addition to what Barry says below, a couple of comments: - You can safely ignore the 'high cpu' warnings if you've already done what you can to optimize the page. You're not going to hit any invisible limits based on them, just the usual CPU quota etc. - If 'eventual' writes are good enough, you may want to look into using the task queue. You can enqueue the write in the task queue, which will do it offline and avoid making the user wait.
-Nick Johnson On Wed, Sep 16, 2009 at 2:11 PM, Prashant <[email protected]> wrote: > hi, > > my app needs to store some data to datastore for each & every request, say > 1 object per request which causes high cpu usage per request. to minimize > the cpu usage per request, instead of adding the object directly to > datastore i add the object to a LinkedList (every request) and use a cron > which moves objects form the LinkedList to datastrore periodically, say > every min. > > I feel it is not a good practice. I don't want to use memcache (instead of > server ram) to store my LinkedList because delay in fetching and storing the > list form/to memcache may cause loss of data from upcomming requests (or > previous request). I don't want to use task queue either for some reasons. > > Experts please comment on this kind of implementation. Losses & Benefits, > any alternative good practice. > > Thanks. > > > > -- Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
