On Thu, Dec 15, 2011 at 8:20 AM, Alan Xing <[email protected]> wrote: > The dollar cost of HRD and MS are the same? It was a surprise for me. I > always had the impression HRD costed way more. Now I could not find that > document except from Google search engine snapshot. As of Dec 10, 2011, GAE > doc still mentioned HRD "uses approximately three times the storage and CPU > cost of the master/slave option". Please see attached snapshot. > > Regardless, I'm very happy to know that HRD is not costing more than MS any > more. I will seriously think about to migrate to HRD soon.
When HRD was launched it did cost 3x more than MS (since it costs Google at least 3x more to do the replication). But the pricing has later adjusted to be the same as MS. Cheers, Brian > As of this moment today, we are still seeing way much higher front end > instance hours than I would have expected before yesterday's spike. I'm not > convinced by the explanations I have received so far. I'd think it is good > to be transparent about pricing. Choosing a platform is a long term > relationship, transparency can help stabilize the relationship. > > > On Wed, Dec 14, 2011 at 12:14 PM, Brian Quinlan <[email protected]> wrote: >> >> On Thu, Dec 15, 2011 at 4:27 AM, Alan Xing <[email protected]> wrote: >> > Yes, we are still using the M/S datastore. We feel that we are not >> > offering >> > mission critical services. These services don't require the HRD level >> > availability. HRD db read/write/store all costs more. >> >> What do you mean? The dollar cost for HRD is the same as MS. >> >> >I know we could save >> > some CPU hours by using Python 2.7 concurrency feature if we move over >> > to >> > HRD. There is loss and there is gain. Overall, we don't see our cost >> > will >> > reduce by moving M/S to HRD. That is why we are reluctant to make the >> > move. >> > >> > I have always wondered why GAE doesn't extend Python 2.7 support to M/S. >> > It >> > doesn't seem there is any particular technical blocker. Maybe I'm wrong. >> > >> > In this random latency case, I again wonder why GAE doesn't plan to fix >> > for >> > M/S servers. >> >> We do have a fix - the HRD :-) Seriously, to make MS more consistent >> and reliable, you'd need to synchronously replicate the data across >> machines and data centers and that is exactly what MRD. >> >> Cheers, >> Brian >> >> > >> > Is the plan to completely phase out M/S servers in some near future? >> > >> > On Wed, Dec 14, 2011 at 1:27 AM, Kenneth <[email protected]> >> > wrote: >> >> >> >> Are you using the old MS datastore or the HR datastore? If you're using >> >> MS >> >> then pretty much anything to do with the datastore is totally random, >> >> so >> >> expect random latency increases which result in higher instance counts >> >> and >> >> thus higher cost to you, randomly of course. Google will not be fixing >> >> these >> >> so move to the hr datastore when you can. >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "Google App Engine" group. >> >> To view this discussion on the web visit >> >> https://groups.google.com/d/msg/google-appengine/-/PsCn4-PDjvUJ. >> >> >> >> 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/google-appengine?hl=en. >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Google App Engine" 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/google-appengine?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" 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/google-appengine?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
