Without knowing what you are doing, as a general suggestion I say use rough approximations and charge per op instead of trying to match App Engine's pricing cent for cent. A few months ago, someone in this group posted a very good analogy about how everyone pays the same amount of money at a buffet even if they eat different amounts of food; that's the level you should be thinking about pricing. Doing your suggested pricing is also difficult because when you turn on multithreading (concurrent requests, you WANT to do this), it will be a bit harder to map exact amount of milliseconds used per request because you could potentially be serving many requests in parallel. We did something similar with cpu_ms pricing before, where some operations always cost a certain amount of ms no matter what, even though in real life there was a lot more variance due to network congestion, CPU congestion, etc.
One more pricing analogy: lawyers have systems that track how long they spend on the phone. They don't do this to pass the cost of the long distance phone call to their clients (cents). They do this so they can (at least in my experience) round up to the nearest 5 minute increment and bill at $400-$1000 dollars an hour. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Fri, Sep 9, 2011 at 2:57 AM, Tom Taylor <ttay...@encircle.co.uk> wrote: > Hi, > We are currently developing a multi-user Java application on App Engine > where we want to pass on the cost of the computing resources used to each > individual user (plus our markup of course). > The computing resources are composed of tasks placed on the task queue. > The url of each item on the task queue can easily be related back to a > specific user. > Inside the tasks we make a few data store calls and some memcache calls and > some urlfetch calls (as we're using the gdata apis to talk to Google apps > apis). > > My question is: we were planning to use the *QuotaService *api to get the > cpu cycles used and charge accordingly - but under the new billing model, as > I understand it, this is no longer appropriate. Can anyone suggest a way > forward with this? > I have set up the appstats module - and it seems all the info I need is > available to do the calculations under the new billing model - but can I get > to this information programatically. I've had a good search through the api > docs and didn't find anything. > > As a side note we are using multi tenancy for the datastore - with the > userid as the namespace. So I think I have the datastore resources used per > user under control. > > regards > > Tom > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/sBsX1KLs7P0J. > 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. > -- 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.
