go - Google appengine, least expensive way to run heavy datastore write cron job? -


I have a Google appengine app that has been written in Go, which has a croning process that is 3: 00 runs at once. This process looks at all the changes that happened with my data during the day and stored some meta data about what happened. My users can run reports on this meta data, which can be seen trends in several months. In this process, about 10-20 lakhs of datastore writes every night, all this works well, but since I have started to run it, since then I have been on Google's monthly bill (approximately 50 / month to about $ 400 / month ) Has seen a significant increase in prices.

I have just one setup. It's a very basic workspace that runs in it, I have not changed the default settings at all. Is this a better way to run this process in the night, which can save me money? I have never messed with Backends (which is now discontinued) or module API, and I know that they have changed a lot of things recently, so I'm not sure where to start looking for any advice Would be greatly appreciated.

View your examples at 3:00 p.m. It may be that GAE spin a lot of them to handle the job. You can configure your job so that it can run less parallel, it will take longer but it will probably only require 1 instance. However, if your database actually writes, then this is the biggest factor, it does not have any major impact Will fall.

You can try to see your data models and indexes. Remember that the cost of each indexed field is 2 extra, so see if you can remove the index from some fields if you do not need it.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -