4 ms·

If I'm reading the current status graphs correctly they're regularly seeing 1.5-2.5 second queries and 400ms direct fetches. That seems unbearably bad. Can anyo

If I'm reading the current status graphs correctly they're regularly seeing 1.5-2.5 second queries and 400ms direct fetches. That seems unbearably bad. Can anyone running mission critical apps on the platform comment?

adora 16y ago
Yeah, it's really, really slow -- and the ETA is 2 weeks! Although I have some faith it'll be fixed sooner. We're thinking of porting over to EC2. If anyone knows of any reliable tool that supports this for production, please feel free to shout. Otherwise, we'll probably be building something ourselves...
- cmelbye 16y ago
  There's always AppScale. It supports EC2 and I think it's been officially recognized by Google. http://code.google.com/p/appscale/ http://code.google.com/p/appscale/ If you write your own, would you consider open sourcing it?
  - adora 16y ago
    Thanks for the link! Appscale looks a bit limited for production use, but definitely will play around with it! Re: open source. We might just brute force it for now. If not, we'll definitely pretty it up at some point and open source it. At the very least we can publish our learnings.
axiom 16y ago
Yeah we've been freaking out about this. We have our app used in the classroom, and have had several sessions disrupted because of this. Needless to say our customers were pissed. We're in the process of doing an emergency move over to EC2 because of these issues. That being said, I must admit that this is a really decent response on Google's part. Unfortunately the problems go deeper than just these latest problems with datastore.
- richardw 16y ago
  What are your more permanent worries?
- aarontcheung 16y ago
  Just wondering, are you porting to mySQL, Cassandra, or HBase? We're currently moving off app engine also, and would love to hear more about your final setup.

4 ms·

If I'm reading the current status graphs correctly they're regularly seeing 1.5-2.5 second queries and 400ms direct fetches. That seems unbearably bad. Can anyo

by TimothyFitz 16y ago

adora 16y ago
Yeah, it's really, really slow -- and the ETA is 2 weeks! Although I have some faith it'll be fixed sooner. We're thinking of porting over to EC2. If anyone knows of any reliable tool that supports this for production, please feel free to shout. Otherwise, we'll probably be building something ourselves...
- cmelbye 16y ago
  There's always AppScale. It supports EC2 and I think it's been officially recognized by Google. http://code.google.com/p/appscale/ http://code.google.com/p/appscale/ If you write your own, would you consider open sourcing it?
  - adora 16y ago
    Thanks for the link! Appscale looks a bit limited for production use, but definitely will play around with it! Re: open source. We might just brute force it for now. If not, we'll definitely pretty it up at some point and open source it. At the very least we can publish our learnings.
axiom 16y ago
Yeah we've been freaking out about this. We have our app used in the classroom, and have had several sessions disrupted because of this. Needless to say our customers were pissed. We're in the process of doing an emergency move over to EC2 because of these issues. That being said, I must admit that this is a really decent response on Google's part. Unfortunately the problems go deeper than just these latest problems with datastore.
- richardw 16y ago
  What are your more permanent worries?
- aarontcheung 16y ago
  Just wondering, are you porting to mySQL, Cassandra, or HBase? We're currently moving off app engine also, and would love to hear more about your final setup.