CODEWITHSUNDEEP
google-app-enginegoogle-cloud-platformgoogle-cloud-datastore
user1961
user1961

Reputation: 1500

Is there a good ratio for Front End Hours to Datastore Reads?

My app has two main costs the Front End Hours and the Datastore Read Ops. The cost ratio is about 1:1, i.e. a typical day will have $100 in Front End hours and $100 in read operations.

Is there an ideal ratio between these services? Obviously this is code dependent but I'm wondering if my ratio raises red flags on its own.

Upvotes: 0

Views: 46

Answers (2)

Ian Loubser
Ian Loubser

Reputation: 459

If you're asking because of cost concern then I've found in 80%+ cases you could always benefit from more caching.

If the data being read from the datastore doesn't change that often then I would say that your costs are on the high end for datastore reads. I would advise you to improve your memcache usage, especially since the free tier usage of memcache on Google Cloud is extremely lenient.

If the data being read from the datastore changes a lot daily then I would expect the costs to be more or less equal, but even still you should be able to bring that down with a proper caching strategy.

Upvotes: 1

skjagini
skjagini

Reputation: 3217

There is no such thing as ratio between Front End hours to Datastore Reads.

If your queries are heavy, lets all you do is search your DB, your Datastore Reads will be huge.

At the same time if you cache your data properly you can minimize your Datastore Reads.

Upvotes: 0

Related Questions