I've started work on version 1.1.3 of gaeutilities which is going to add a flag to not save new sessions by default, as well as adding a save method. I've got the first bit of functionality live on a site that every hour has a script that connects and adds anywhere from 80-150 items to my datastore. The script doesn't store cookies, so every request started a new session.
Last night, since adding the new sessions code in, there is a noticeable (though not dramatic) decrease in the CPU Seconds Used/ Second. My suggestion for anyone using sessions is to avoid using datastore backed sessions for anonymous users. gaeutilities with version 1.1.3 will make this easier. Those of you using memcache or pure cookie solutions should not have the overhead that the datastore backed cookies bring to the table, so this may be less of an issue for you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
