mcilwain cb80a0df1e Batch contact/host loads when checking pending delete ... I'm actually surprised that we had this in our code, as it seems like a huge oversight, but we were individually loading each and every referenced contact and host during domain/application create/update/allocate flows. Loading them all as a single batch should reduce round trips to Datastore by a good deal, thus improving performance. We aren't giving up any transactional consistency in doing so and the only potential downside I can think of is that we're always loading all contacts/ hosts instead of only some of them, in the rare case that one of the earlier contacts/hosts is actually in pending delete (which allowed short-circuiting). However, the gains from only making one round-trip should swamp the potential losses in occasionally loading more data than is strictly necessary. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=186656118		2018-03-06 18:50:04 -05:00
..
com/google/testing/builddefs	Update copyright year on all license headers	2017-02-02 16:27:22 -05:00
google/registry	Batch contact/host loads when checking pending delete	2018-03-06 18:50:04 -05:00