p4 sizes

Synopsis

Syntax

Description

Use the -a option to see how much space is occupied by each individual revision in the specified revision range, rather than just the highest revision in the specified range. One line of output is provided per file, per revision.

Use the -s option to obtain the sum of all files specified. Only one line of output is provided, showing the file specification, the number of files summarized, the total number of bytes required, and (if the -b option is provided) the total number of blocks required.

Options

-a	Include all revisions within the range, rather than just the highest revision in the range.
-b blocksize	Display results in blocks of blocksize bytes. Each accumulated file size is rounded up to the nearest blocksize bytes.
-s	Calculate the sum of the file sizes for the specified file argument.
g-opts	See the Global Options section.

Usage Notes

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
N/A	N/A	list

• The p4 sizes command is functionally similar to the UNIX du command.

• If no revision range is specified, the implicit revision range of #1 through #head is assumed.

• File sizes are based on the normalized (UNIX linefeed convention) and uncompressed version of the depot file, regardless of how the file is represented when synced to a client workspace.

Examples

p4 sizes file.c	Show the size of the head revision of file.c in the depot.
p4 sizes -a file.c	Show the sizes of each revision of file.c stored in the depot.
p4 sizes -s -a file.c	Show the total size of all revisions of file.c stored in the depot.
p4 sizes -s -a -b 512 //depot/...	Show the number of files and the total diskspace (in bytes and 512-byte blocks) currently used by a Perforce Server hosting //depot/...
p4 sizes -s //workspace/...	Show the number of files and the total local diskspace (in bytes) required to sync the head revisions of files mapped to the client workspace named workspace.