bvsimmons Posted March 22, 2011 Report Share Posted March 22, 2011 I am having some performance issues with Plastic SCM. I have previously evaluated Plastic and speed was never an issue but now it is. I am using the latest build that you have released. On one of my workstations I executed the command "cm update . --noparallel --stats --timer" I got the results as shown in workstation_plastic The Server is Window 2008 VM (VMWare Server) and the workstation is a Windows 7 VM (Mac OS Parallels). I am using the standard configuration and do not have antivirus installed on either system. Now when I run the above command directly on a workspace created on the server the result is much better as shown in the attached file plastic_server: Link to comment Share on other sites More sharing options...
bvsimmons Posted March 22, 2011 Author Report Share Posted March 22, 2011 I got a error attempting to upload the attached file so I have included them here. Any help ? plastic_server================================= C:\Users\bsimmons\Documents\PlasticSCM\iCSPRG2>cm update . --noparallel --stats --timer SolveSelector 2156 ms Obtain WorkspaceContent 15 ms Update wk revs 0 ms Download time 0 ms Big files 0 ms Big files download 0 ms. 0 times Big files uncompress 0 ms. 0 times Big files write 0 ms Small file 0 ms Small files download 0 ms Small files uncompress 0 ms Small files write 0 ms Total downloaded data size 0.00 Mb Total uncompress 0 ms. 0 times Total write time to open stream 0 ms Create File Streams 0 ms Update wk revs (down) 0 ms. 0 times Protect CO 0 ms Update wk content 0 ms Adjust file 0 ms Set non read only 0 ms, 0 times Set read only 0 ms, 0 times Set Item FSProtection 0 ms, 0 times Set TimeStamp 0 ms, 0 times Gen messages 0 ms Check dir on disk (DirectoryExists + CorrectPathCase + CreateDirectory) 16 ms Print info 0 ms Obtain CO 0 ms Delete wkrev 0 ms, 1 times Get content for item 0 ms Get content for path 0 ms Renames 0 ms Moves 0 ms Set item as deleted 0 ms Get item handler 0 ms FileExists check 15 ms, 2 times DirectoryExist check 0 ms, 1 times GetFSNodes + build PathResolver 0 ms CheckChanged 0 ms, 0 times ChangedCalcHash 0 ms, 0 times File preserved: PreservedCalcHash 0 ms, 0 times PreservedFile 0 ms, 0 times Update process 2266 ms Initial actions 2187 ms SolveSelector 2156 ms Obtain WorkspaceContent 15 ms Obtain CO 0 ms Update content 47 ms Update files 0 ms, 116 times Update diretories 31 ms, 9 times Final actions 0 ms Save workspace 0 ms 5047 ms ================================= plastic_workstation================================= C:\Users\bsimmons\PlasticSCM\iCSPRG>cm update . --noparallel --stats --timer SolveSelector 21672 ms Obtain WorkspaceContent 16 ms Update wk revs 0 ms Download time 0 ms Big files 0 ms Big files download 0 ms. 0 times Big files uncompress 0 ms. 0 times Big files write 0 ms Small file 0 ms Small files download 0 ms Small files uncompress 0 ms Small files write 0 ms Total downloaded data size 0.00 Mb Total uncompress 0 ms. 0 times Total write time to open stream 0 ms Create File Streams 0 ms Update wk revs (down) 0 ms. 0 times Protect CO 0 ms Update wk content 0 ms Adjust file 0 ms Set non read only 0 ms, 0 times Set read only 0 ms, 0 times Set Item FSProtection 0 ms, 0 times Set TimeStamp 0 ms, 0 times Gen messages 0 ms Check dir on disk (DirectoryExists + CorrectPathCase + CreateDirectory) 31 ms Print info 0 ms Obtain CO 0 ms Delete wkrev 0 ms, 1 times Get content for item 0 ms Get content for path 0 ms Renames 0 ms Moves 0 ms Set item as deleted 0 ms Get item handler 0 ms FileExists check 0 ms, 2 times DirectoryExist check 0 ms, 1 times GetFSNodes + build PathResolver 63 ms CheckChanged 0 ms, 0 times ChangedCalcHash 0 ms, 0 times File preserved: PreservedCalcHash 0 ms, 0 times PreservedFile 0 ms, 0 times Update process 21907 ms Initial actions 21735 ms SolveSelector 21672 ms Obtain WorkspaceContent 16 ms Obtain CO 0 ms Update content 125 ms Update files 0 ms, 116 times Update diretories 125 ms, 9 times Final actions 15 ms Save workspace 0 ms 44250 ms ================================= Link to comment Share on other sites More sharing options...
psantosl Posted March 22, 2011 Report Share Posted March 22, 2011 Hey, that's a detailed report!! Look, part of the problem seems to be selector resolution (21 secs) but, since it is done on the server, it seems the problem is due to the network. It seems it is taking all time not on the calculation itself but arriving to the client. It could be a IP issue or a network name issue (I experienced this problem several times with misconfigured machines). Try cm lrep yourserver_by_ip:port -wks=yourserver_by_ip:port and the same with cm lrep yourserver_by_name:port -wks=yourserver_by_name:port Let's check. Also, there could be a disk IO issue too (another 20 seconds lost without a reason), but let's check first the networking issue. pablo Link to comment Share on other sites More sharing options...
bvsimmons Posted March 22, 2011 Author Report Share Posted March 22, 2011 Hey Pablo, You are correct it something in my network... looking at the powershell out below, the lrep command takes 20 seconds when I access by name and 1 second when I access by ip address PS C:\Users\bsimmons> Get-Date Tuesday, March 22, 2011 3:34:02 PM PS C:\Users\bsimmons> cm lrep ssclight:8084 1 default ssclight:8084 PS C:\Users\bsimmons> Get-Date Tuesday, March 22, 2011 3:34:24 PM PS C:\Users\bsimmons> cm lrep 192.168.7.121:8084 1 default 192.168.7.121:8084 PS C:\Users\bsimmons> Get-Date Tuesday, March 22, 2011 3:34:25 PM How do I switch to use my IP address instead of the name of the server while I debug the network issue? What else should I try to check the potential disk problem you mentioned? Thanks Bernard Link to comment Share on other sites More sharing options...
psantosl Posted March 22, 2011 Report Share Posted March 22, 2011 Hi! Ok, let's start with the network issue: you can do several things: configure your client to access your server by IP (plastic --configure). But, there's another way too: you can edit server.conf and add a <ServerName></ServerName> entry and add you IP there (server IP), then you'll always get this name when contacting from the client. But, anyway, the client configuration should be more than enough. Now, the disk: well, if you're running on a vmachine, first check the host IO is not going crazy... I've seen this happening on linux boxes serveral times (vmware server). Let's check this first and then come up with more ideas. Link to comment Share on other sites More sharing options...
bvsimmons Posted March 22, 2011 Author Report Share Posted March 22, 2011 Ok, that speeds everything up..., Client Startup, Check-out, all Client Operations, everything is faster.. On my Workstation VM the "SolveSelector" is now 219 ms, but the Obtain WorkspaceContent is now 21141 ms, the total time displayed at the end is now 22109 ms down from 44250 ms, which is a better that 50% reduction... Now do you want me to check the I/O on the Server VM or the WorkStation VM? Thanks Bernard Link to comment Share on other sites More sharing options...
psantosl Posted March 23, 2011 Report Share Posted March 23, 2011 Ok, first check that your host machine (your Mac OS X) is not overusing the HD. On Linux we use "iotop" but you'll have to find something similar for Mac. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.