Need help tracking "datastore transaction or write too big" warnings

154 views
Skip to first unread message

Pol

unread,
Oct 14, 2011, 6:03:46 AM10/14/11
to Google App Engine
Hi,

With some clients of our system, we're getting some "datastore
transaction or write too big" exceptions on transaction commits. The
requests takes 1mn and the process even exceeds the soft size limit
and gets killed, so it's pretty bad.

What are we hitting there? A maximum serialized entity size? What are
these exact limits?

Thanks,

- Pol

Simon Knott

unread,
Oct 14, 2011, 6:25:21 AM10/14/11
to google-a...@googlegroups.com
The maximum size of an individual entity is 1MB for the datastore - http://code.google.com/appengine/docs/java/datastore/overview.html#Quotas_and_Limits

Apart from that limit, I'm not sure what write limits there are for the datastore for an individual transaction.

Pol

unread,
Oct 14, 2011, 3:09:04 PM10/14/11
to Google App Engine
Can anyone comment from Google comment on this 2nd point: write limits
on entire transaction? Our entities are 4KB on average so I'm trying
to track down what's happening but debugging on the server in a live
product is really not trivial.

On Oct 14, 12:25 pm, Simon Knott <knott.si...@gmail.com> wrote:
> The maximum size of an individual entity is 1MB for the datastore -http://code.google.com/appengine/docs/java/datastore/overview.html#Qu...

Timofey Koolin

unread,
Oct 14, 2011, 3:33:08 PM10/14/11
to google-a...@googlegroups.com
if you use XG (cross group) transactions - you can use no more than 5 entity groups in transaction.

2011/10/14 Pol <p...@everpix.net>
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.




--
С уважением,
Кулин Тимофей.

Телефон: +7 (4852) 974793
ICQ: 114902104
email: tim...@koolin.ru
Blog: http://timofey.koolin.ru
Reply all
Reply to author
Forward
0 new messages