Change-Id: I052c2b3cc3440f081ef11ba5d999bf8e7f230c6a
Reviewed-on: https://go-review.googlesource.com/35450Reviewed-by: Russ Cox <rsc@golang.org>

This allows easily adding additional information when uploading
existing files. Example usage:

benchsave -header <(echo goarch: arm; echo goos: linux) *.log

Change-Id: I46afafd39d8314d9c06c209f868b71cd5e58c63a
Reviewed-on: https://go-review.googlesource.com/35350Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: Ib29820f8574a3ba09fce8079f75b933011ef2cee
Reviewed-on: https://go-review.googlesource.com/35267Reviewed-by: Russ Cox <rsc@golang.org>

The MySQL protocol requires 1-3 synchronous round-trips for every
INSERT statement; to reduce the overhead, we now batch up 900 label
INSERT statments at a time. This makes a massive difference;
TestQuery previously ran in 108s; with this change, it now runs in 5s.

We were also affected by golang/go#15606; since we now generate a new INSERT
statement for every record, we are sidestepping that issue.

Change-Id: Id7a56c18c0978470542135894a2f2bcf6f7c9dd1
Reviewed-on: https://go-review.googlesource.com/35266Reviewed-by: Russ Cox <rsc@golang.org>

The MySQL protocol and database/sql require several round-trips to
execute queries with placeholders. Setting interpolateParams will
cause the mysql client library to interpolate the arguments and issue
a single string query to the server, reducing the number of round
trips. See
https://www.vividcortex.com/blog/2014/11/19/analyzing-prepared-statement-performance-with-vividcortex/

Change-Id: I766d593e9981c7ce2fbb1b48fe919ab46699416c
Reviewed-on: https://go-review.googlesource.com/35264Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: Ica64b354cbf8f9bd43344459fac860a2c816d209
Reviewed-on: https://go-review.googlesource.com/35263Reviewed-by: Russ Cox <rsc@golang.org>

ReplaceUpload removes any records for an upload so that those records
can be reinserted in the database.

Change-Id: I8fa0701b72c3ace380d3c7922df0c17b81a0d426
Reviewed-on: https://go-review.googlesource.com/35257Reviewed-by: Russ Cox <rsc@golang.org>

Instead of simply sequentially-increasing upload IDs, we now generate
one with a date prefix.

Change-Id: Id54ab88e6d76932cfc121183ea2da5d145599d16
Reviewed-on: https://go-review.googlesource.com/35256Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: I11df054853be604fcabec6f20da7f34c970d7bfa
Reviewed-on: https://go-review.googlesource.com/35154Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: I6220ec86c80c07899b1e511753a07da54e5e7bbd
Reviewed-on: https://go-review.googlesource.com/35153Reviewed-by: Russ Cox <rsc@golang.org>

This also moves the metadata generation into processUpload; it didn't
really benefit from being in a separate function.

Change-Id: Ia9fb3455cf8851ea89171bc7e135d69e6734eafc
Reviewed-on: https://go-review.googlesource.com/35210Reviewed-by: Russ Cox <rsc@golang.org>

Reuse a single transaction for all INSERT statements for a single
upload. This cuts about 50% of the runtime off an invocation of
the tests with -cloud, and about 25% of the runtime off an /upload run
on App Engine.

Change-Id: I90068f60420cfb67ae693f18ed83b341c2e483bd
Reviewed-on: https://go-review.googlesource.com/35069Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: I5e10082adc66e51898a71e1a67da7833f287af9d
Reviewed-on: https://go-review.googlesource.com/35067Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: Ie3c5d4adae68cd81290ec4d8b53d5db0cf814a71
Reviewed-on: https://go-review.googlesource.com/35065Reviewed-by: Chris Broadfoot <cbro@golang.org>

Change-Id: Ia48bc4e1bb918b4d2e28752cfe45f31ac9955e47
Reviewed-on: https://go-review.googlesource.com/35055Reviewed-by: Russ Cox <rsc@golang.org>

Apparently this is why I was explicitly naming /upload and /search.

Change-Id: Ibdb24f8eac83ae6bac61dacb625f500c28512291
Reviewed-on: https://go-review.googlesource.com/35066Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: I060d45ac3b487900ab8315978fe89ab576c571b7
Reviewed-on: https://go-review.googlesource.com/35053Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: Ifb1baf9a94c28167bedf61c4c2495b724349bdf3
Reviewed-on: https://go-review.googlesource.com/35052Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: Ie4f48245e1f223486557921a4196570c430e5feb
Reviewed-on: https://go-review.googlesource.com/34934Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: Id8fe9565bee87f824d6efbff3f983f0170534603
Reviewed-on: https://go-review.googlesource.com/34933Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: Id6bff920866bc175aaf18f839dc7ab2487e8adf6
Reviewed-on: https://go-review.googlesource.com/34931Reviewed-by: Russ Cox <rsc@golang.org>

Change-Id: Icef3215b69d220620c9bdc44150699abbce1c57e
Reviewed-on: https://go-review.googlesource.com/34834Reviewed-by: Russ Cox <rsc@golang.org>

This change parses incoming benchmark records in parallel to writing
them to Google Cloud Storage. It does not yet attempt to insert the
parsed records into Cloud SQL.

Change-Id: I250b334569b8d59f2366025db5c56add51b96bd6
Reviewed-on: https://go-review.googlesource.com/34628Reviewed-by: Russ Cox <rsc@golang.org>

BenchmarkReader is capable of reading standard benchmark files into
Result objects and writing those Result objects back out to a Writer.

Change-Id: I022221f53b5d3ce1de7e8e7b74d265a50ac4a0eb
Reviewed-on: https://go-review.googlesource.com/34627Reviewed-by: Russ Cox <rsc@golang.org>

This creates the skeleton of an AppEngine app for perfdata.golang.org
and adds an initial implementation of /upload that saves the provided
file into Cloud Storage.

Change-Id: I1fe19b27841ab62aad146d1d1019996634012d35
Reviewed-on: https://go-review.googlesource.com/34620Reviewed-by: Russ Cox <rsc@golang.org>