You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using p4-fusion with a Perforce proxy server, it is sometimes beneficial for performance debugging purposes to know the proxy cache hit/miss rate while downloading files through p4 print
This is usually done by adding a -Zproxyverbose tag in the p4 CLI:
p4 -Zproxyverbose sync
We can specify the same tag when we create the P4API contexts.
When using p4-fusion with a Perforce proxy server, it is sometimes beneficial for performance debugging purposes to know the proxy cache hit/miss rate while downloading files through
p4 print
This is usually done by adding a
-Zproxyverbose
tag in the p4 CLI:We can specify the same tag when we create the P4API contexts.
p4-fusion/p4-fusion/p4_api.cc
Line 50 in 6746b60
And then we should be able to log that information through p4-fusion, either simply to stdout or add it in the commit message
The text was updated successfully, but these errors were encountered: