Home | History | Annotate | Download | only in histograms

Lines Matching full:upload

1033 <histogram name="Autofill.ServerExperimentId.Upload"
1036 The experiment ID received at the time of an Autofill upload.
8012 rapidly as possible, just after successfully sending an UMA upload. Each
8026 rapidly as possible, just after successfully sending an UMA upload. Each
8039 rapidly as possible, just after successfully sending an UMA upload. If no
8178 UDP as rapidly as possible, just after successfully sending an UMA upload.
8196 possible, just after successfully sending an UMA upload. Each packet was
8207 possible, just after successfully sending an UMA upload. Each packet was
8216 possible, just after successfully sending an UMA upload. If no packets (of
8225 UDP as rapidly as possible, just after successfully sending an UMA upload.
8320 UDP as rapidly as possible, just after successfully sending an UMA upload.
12188 The number of microseconds it took to upload a tile's full texture as
13001 The size of the upload data for CheckClientDownloadRequest URLFetchers.
13265 Final result of attempt to upload binary to download feedback service.
14695 For each attempted UMA upload, log whether the upload was successfully
14696 constructed. An upload might fail to be constructed, for example, if we try
14697 to upload before the system is fully initialized; or if serialization of the
14705 For each upload to the protocol buffer (v2) UMA server, log whether the
14706 upload was successful, or whether there was an error.
14712 For each upload to the XML (v1) UMA server, log whether the upload was
22861 <group name="tbar1" label="Use only Toolbar upload data"/>
23634 sending an UMA upload. Each packet was numbered, as was its ACK
23979 client successfully sent a UMA upload. Each packet was numbered