谷歌应用程序引擎过多的数据存储小操作 [英] Google app engine excessive datastore small operations

问题描述

我的网站有大约50个用户，我收到了过多的小型数据存储操作。我积极地memcaching，没有那么多的记录，我仍然得到数百万的小型数据存储操作。 Appstats表示成本为0，但实际成本不为0.
我基本知道小数据存储操作可能发生的位置。

主要操作：这但我memcache它，直到数据没有改变。此外，我的大部分关键操作都有限制= 100（这是最大），所以要获得12米的操作，我需要拨打120000个电话（我假设提取1个键是1个小操作）。由于我每天约有60-70次访问，似乎有点过分。
我只是不知道是什么原因导致了很多操作。 Appstats让我不知道。

这是仪表板。

是appstats。

解决方案

您是否使用了很多 counts ？似乎可以成为问题导致过度使用数据存储小操作。

我没有你的代码，但是这个答案在遇到此问题时有一些优化代码的建议。

另外，请看一下类似的问题 - Google应用引擎过多的小型数据存储操作，以获得相似的答案。

My site has about 50 users and I am getting excessive small datastore operations. I am aggressively memcaching, dont have that many records and still I get millions of small datastore operations. Appstats says the cost is 0 yet the real cost is not 0. I basically know where the small datastore operations might occur.

Key only operations: I do this but I memcache it until the data is not changed. Plus most of my key only operation have limit=100 (this is max) so to get 12m operations I would need to make 120000 calls (I am assuming fetching 1 key is 1 small operation). As I get about 60-70 visits a day that seems a bit excessive. I just cant figure out what is causing that many operations. Appstats is giving me no clue.

This is the dashboard.

This is the appstats.

解决方案

Are you using lots of counts? Seems like this can be a problem that causes excessive datastore small operations.

I don't have your code, but this answer has some suggestions for optimizing your code when experiencing this problem.

Also, take a look at a similar question - Google app engine excessive small datastore operations for similar answers

这篇关于谷歌应用程序引擎过多的数据存储小操作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！