> The GAE datastore is pretty slow. From what I've gathered, depending > on your data model, if you're doing more than 2 read/writes (with > writes being *much* slower) per request, you'll probably have issues.
Yes I did a small test with a simple model. It was taking around 1sec/request for single write on an entity. I am not sure if that is acceptable in real world apps. As Robin mentioned earlier, we can use batch write to speed up writes. Probably read should be much faster & it can cached to have even better response. My only concern is web2py is more of database neutral & because of this many of GQL's specific features are'nt directly supported. Make no mistake. Web2py is a great framework with a very lively community. Infact I feel there are certain things done better than rails. But for my current requirement, I think I have staty close to GAE's api to extract every bit of performance improvement. So I have started to dive into GAE to find out how much I will be missing if I choose web2py for google apps. Is there someone using production application in GAE using web2py? If so what is the performance? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
