[p4] Slowdown and unquoted wildcard paths
jare at pyrostudios.com
Mon Jun 5 08:46:01 PDT 2006
In our Windows-based Perforce installation, we sometimes notice that a
P4V navigation operation (for example, opening a folder to explore its
contents) suddenly takes a long time to start, then everything goes
blazingly fast for a number of minutes, then we get the slowdown again.
At first I thought that it might be due to the database being blocked
during transfer of huge files. However, this is not the case. Major data
transfers are very rare, and the slowdown appears frequently (if
In the docs I finally found a good hint:
"In some cases, p4 commands using unquoted filepatterns with a
combination of depot syntax and wildcards, such as:
p4 files //depot/*
can result in a delayed response on Windows. You can prevent the delay
by putting double quotes around the file pattern"
Now this makes a lot of sense, because in fact the P4V client program
doesn't seem to be putting double quotes around such commands, which are
precisely the ones where we notice the slowdown. The pattern of this
slowdown seems consistent with the Windows networking timings. However,
due to this erratic behaviour, I haven't been able to verify if this is
actually the problem.
- Has anyone encountered found P4V to be a known offender in this area?
- Should I notify this potential problem in P4V to the Support team?
Thanks in advance,
More information about the perforce-user