Shallow flush after calling beginSetPixels

cc/tile_manager.cc

Index: cc/tile_manager.cc
diff --git a/cc/tile_manager.cc b/cc/tile_manager.cc
index 58e3b3df2f2f787f24b9b639a47bca1ab8032335..5ad985ec81efc0b8a222304b69d1408d22066bbc 100644
--- a/cc/tile_manager.cc
+++ b/cc/tile_manager.cc
@@ -549,6 +549,8 @@ void TileManager::OnRasterTaskCompleted(
     resource_pool_->resource_provider()->beginSetPixels(resource->id());
     managed_tile_state.resource = resource.Pass();
     tiles_with_pending_set_pixels_.push(tile);
+
+    resource_pool_->resource_provider()->shallowFlushIfSupported();

[epenner, 2013/01/10 04:45:49]

Could this just go straight into the resource provider?

In general I'm starting to think the upload query and flushes should come out of
the resource provider so we could do things in batches rather than do everything
per-upload (query / flush / etc.)  But maybe the overhead is negligible? It
looks significant on traces, but maybe that's just tracing overhead?

[reveman, 2013/01/10 14:46:58]

I think the tile manager is the right place for this. Batches might be the way
to go but I think that should be controlled by the tile manager rather than
being hidden behind the resource provider interface.

[epenner, 2013/01/10 17:34:42]

Yeah sorry, this patch is good as is, just thinking out loud on the batching.

But could shallowFlush call not just go in beginSetPixels for now?  Seems like
we could benefit on any beginSetPixels call.

[epenner, 2013/01/10 17:45:42]

So actually I talked with Dave and this is good as is. The flush can later be
used to kick off batches of uploads, which means it should stay outside of
resource provider.

   } else {
     resource_pool_->resource_provider()->releasePixelBuffer(resource->id());
     resource_pool_->ReleaseResource(resource.Pass());