Hi Cornel, One possible cause that the data upload might be more expensive the second time around is if you had created indexes after the initial upload. If you have a large amount of data and your application is not yet being used, it is often best to upload the data, then create indexes. The index creation time might be longer, but you'll save on API CPU cost. This is just one possibility, I think I'd need to know more about your application.
Thank you, Jeff On Tue, Sep 1, 2009 at 9:05 AM, Cornel <corneliu.lupu...@gmail.com> wrote: > > Hello! > > I tried to upload my database from a *.csv file using the appcfg.py > tool. The file has about 35MB. > > The first time i uploaded (several weeks ago) it consumed about 70% > CPU Quota. > Later i deleted the database. > > Today i tried to upload again, but the quota got 95% and it only > uploaded about half of the database. (I also got a lot of "HTTPError: > HTTP Error 403: Forbidden" errors). > > My question is, where does the difference in CPU Quota come from > (considering it was the same script and the same input file) ? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
