Open MPI logo

MTT Devel Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all MTT Devel mailing list

Subject: [MTT devel] MTT GDS -- one more...
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2010-02-11 21:43:21

Heh... even more questions...

(BTW, Ethan and I have asked soooo many questions that if it helps, I can setup a webex and we can all discuss this in person rather than via 1,000,000 annoying emails from us. :-) Webex can call you; no one will need to pay for an international call)

1. It looks like the main benefits of using the Google App Engine -- specifically for MTT -- is that we can use the GDS and/or we can host an application on their web servers. Is that correct?

2. In reading through the Google Appengine docs, the GDS stuff looks like we mainly can access the data through GQL. I don't see any mention of doing map/reduce kinds of computations (Ethan and I were talking on the phone today about MTT Appengine possibilities). I'm new to all this stuff, so it's quite possible that a) I missed it, or b) I just don't understand what I'm seeing/reading yet. Or does GQL do map/reduce on the back end to do its magic? Is GQL the main/only way we have to access GDS?

3. Is there a reason that doesn't use the python API to directly talk to GDS? I.e., what is the rationale for using a web app on appengine? Is the web app doing stuff that we can't do at the client? Ditto for and (these questions are partially fueled by my curiosity and concern about why we're using so much CPU at Google)

Jeff Squyres
For corporate legal information go to: