In case of p4 server is busy with a large request, nifty perforce does too many
retries, causing resource usage on p4 server.
Maybe exponential backoff would help.
Process log on p4 server:
17160 R user 00:02:02 edit D:\work\ProcessCmd.cpp
17164 R user 00:02:02 edit D:\work\ProcessCmd.cpp
17168 R user 00:02:02 edit D:\work\ProcessCmd.cpp
17172 R user 00:02:02 edit D:\work\ProcessCmd.cpp
17176 R user 00:02:03 edit D:\work\ProcessCmd.cpp
17180 R user 00:00:02 edit D:\work\ProcessCmd.cpp
17188 R user 00:01:07 edit D:\work\ProcessCmd.cpp
17192 R user 00:01:05 edit D:\work\ProcessCmd.cpp
17208 R user 00:01:05 edit D:\work\ProcessCmd.cpp
17212 R user 00:01:07 edit D:\work\ProcessCmd.cpp
17224 R user 00:01:05 edit D:\work\ProcessCmd.cpp
17228 R user 00:01:06 edit D:\work\ProcessCmd.cpp
17232 R user 00:01:05 edit D:\work\ProcessCmd.cpp
17236 R user 00:02:00 edit D:\work\ProcessCmd.cpp
17240 R user 00:02:00 edit D:\work\ProcessCmd.cpp
Original issue reported on code.google.com by fsiegm...@gmail.com on 9 Dec 2011 at 2:10
Original issue reported on code.google.com by
fsiegm...@gmail.com
on 9 Dec 2011 at 2:10