Re: [p4] Perforce Performance with Lots Binary Files

itechnology <[email protected]>
Newsgroups gmane.comp.version-control.perforce
Message-ID <[email protected]>
Posted on behalf of forum user 'itechnology'.

I did some preliminary optimizations for where i work.
As Garry pointed out, try to make sure perforce is not trying to compress
already compressed files.

You can do this by typing "p4 typemap" and telling perforce how to
treat different filetypes. For example here is the list i came up with after
analyzing all the kinds of stuff i discovered that was being stored in perforce
..copy paste the list ..extend it, and/or adapt it to your usage style:

text //spec/... binary+F //depot/....ai binary+F //depot/....aiff binary+F
//depot/....apk binary+F //depot/....aqt binary+F //depot/....avi binary+F
//depot/....bdsp binary+F //depot/....bcmap binary+F //depot/....bin binary+F
//depot/....bmp binary+F //depot/....cab binary+F //depot/....car binary+F
//depot/....chm binary+F //depot/....cpl binary+F //depot/....ctx binary+F
//depot/....cur binary+F //depot/....db binary+F //depot/....dbmdl binary+F
//depot/....dll binary+F //depot/....doc binary+F //depot/....ds_store binary+F
//depot/....eot binary+F //depot/....exe binary+F //depot/....flv binary+F
//depot/....frx binary+F //depot/....gif binary+F //depot/....grm binary+F
//depot/....ico binary+F //depot/....icns binary+F //depot/....img binary+F
//depot/....jar binary+F //depot/....jks binary+F //depot/....jpg binary+F
//depot/....jpeg binary+F //depot/....key binary+F //depot/....keystore binary+F
//depot/....ldf binary+F //depot/....lib binary+F //depot/....nib binary+F
//depot/....m4v binary+F //depot/....me binary+F //depot/....mdb binary+F
//depot/....mdf binary+F //depot/....mmt binary+F //depot/....mov binary+F
//depot/....mp3 binary+F //depot/....mp4 binary+F //depot/....nupkg binary+F
//depot/....obj binary+F //depot/....ogg binary+F //depot/....ogv binary+F
//depot/....otf binary+F //depot/....p7b binary+F //depot/....p12 binary+F
//depot/....pdb binary+F //depot/....pdf binary+F //depot/....pfx binary+F
//depot/....pdn binary+F //depot/....png binary+F //depot/....psb binary+F
//depot/....psd binary+F //depot/....psp binary+F //depot/....res binary+F
//depot/....rpt binary+F //depot/....rtf binary+F //depot/....scc binary+F
//depot/....sdb binary+F //depot/....sdf binary+F //depot/....snk binary+F
//depot/....so binary+F //depot/....sqlite binary+F //depot/....sqlite3 binary+F
//depot/....swiftdoc binary+F //depot/....swiftmodule binary+F //depot/....swf
binary+F //depot/....swp binary+F //depot/....tlb binary+F //depot/....tif
binary+F //depot/....tiff binary+F //depot/....ttf binary+F //depot/....wav
binary+F //depot/....webm binary+F //depot/....wmv binary+F //depot/....woff
binary+F //depot/....woff2 binary+F //depot/....xcuserstate binary+F
//depot/....xps binary+F //depot/....zip binary+F //depot/....zsh 



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/1134-perforce-performance-with-lots-binary-files
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.