perfdiag - Run performance diagnostic
gsutil perfdiag [-i in.json] gsutil perfdiag [-o out.json] [-n objects] [-c processes] [-k threads] [-p parallelism type] [-y slices] [-s size] [-d directory] [-t tests] [-j ratio] gs://<bucket_name>...
The perfdiag command runs a suite of diagnostic tests for a given Google Storage bucket.
The 'bucket_name' parameter must name an existing bucket to which the user has write permission. Several test files will be uploaded to and downloaded from this bucket. All test files will be deleted at the completion of the diagnostic if it finishes successfully.
gsutil performance can be impacted by many factors at the client, server, and in-between, such as: CPU speed; available memory; the access path to the local disk; network bandwidth; contention and error rates along the path between gsutil and Google; operating system buffering configuration; and firewalls and other network elements. The perfdiag command is provided so that customers can run a known measurement suite when troubleshooting performance problems.
Providing Diagnostic Output To Cloud Storage Team
If the Cloud Storage Team asks you to run a performance diagnostic please use the following command, and email the output file (output.json) to email@example.com:
gsutil perfdiag -o output.json gs://your-bucket
|-n||Sets the number of objects to use when downloading and uploading files during tests. Defaults to 5.|
|-c||Sets the number of processes to use while running throughput experiments. The default value is 1.|
Sets the number of threads per process to use while running throughput experiments. Each process will receive an equal number of threads. The default value is 1.
Sets the type of parallelism to be used (only applicable when threads or processes are specified and threads * processes > 1). The default is to use fan. Must be one of the following:
|-y||Sets the number of slices to divide each file/object into while transferring data. Only applicable with the slice (or both) parallelism type. The default is 4 slices.|
Sets the size (in bytes) for each of the N (set with -n) objects used in the read and write throughput tests. The default is 1 MiB. This can also be specified using byte suffixes such as 500K or 1M.
|-d||Sets the directory to store temporary local files in. If not specified, a default temporary directory will be used.|
Sets the list of diagnostic tests to perform. The default is to run the lat, rthru, and wthru diagnostic tests. Must be a comma-separated list containing one or more of the following:
Adds metadata to the result JSON file. Multiple -m values can be specified. Example:
gsutil perfdiag -m "key1:val1" -m "key2:val2" gs://bucketname
Each metadata key will be added to the top-level "metadata" dictionary in the output JSON file.
|-o||Writes the results of the diagnostic to an output file. The output is a JSON file containing system information and performance diagnostic results. The file can be read and reported later using the -i option.|
|-i||Reads the JSON output file created using the -o command and prints a formatted description of the results.|
|-j||Applies gzip transport encoding and sets the target compression ratio for the generated test files. This ratio can be an integer between 0 and 100 (inclusive), with 0 generating a file with uniform data, and 100 generating random data. When you specify the -j option, files being uploaded are compressed in-memory and on-the-wire only. See cp -j for specific semantics.|
The perfdiag command ignores the boto num_retries configuration parameter. Instead, it always retries on HTTP errors in the 500 range and keeps track of how many 500 errors were encountered during the test. The availability measurement is reported at the end of the test.
Note that HTTP responses are only recorded when the request was made in a single process. When using multiple processes or threads, read and write throughput measurements are performed in an external process, so the availability numbers reported won't include the throughput measurements.
The perfdiag command collects system information. It collects your IP address, executes DNS queries to Google servers and collects the results, collects network statistics information from the output of netstat -s, and looks at the BIOS product name string. It will also attempt to connect to your proxy server if you have one configured and will look up the location and storage class of the bucket being used for performance testing. None of this information will be sent to Google unless you choose to send it.