Any updates on this? I'm still having this issue.
Keith
-----Original Message-----
From: sos-list-admin@xxxxxxxxxxxxxxxxxxxx
[mailto:sos-list-admin@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Linda Bauer
Sent: Wednesday, March 17, 2004 9:24 AM
To: Keith Kemp; sos-list@xxxxxxxxxxxxxxxxxxx
Subject: RE: [SOS-LIST] SOSCMD and CPU Usage
Hi, Keith,
Ok, we'll see if we get this same behavior in house. We really haven't done
extensive performance testing on the CLC.
Thanks for the feedback.
Linda Bauer
SourceGear
Technical Support
visit our support forum at
http://support.sourcegear.com
At 06:51 PM 3/16/2004, Keith Kemp wrote:
>Not the entire thing, it gets to a point and then does....
>
>It uses a lot of memory too, 120MB+ and 150+ virtual memory.
>
>Yeah, I was just saying all it's doing is downloading files, not computing
>pi...
>
>-----Original Message-----
>From: Linda Bauer [mailto:Linda@xxxxxxxxxxxxxx]
>Sent: Tuesday, March 16, 2004 7:26 AM
>To: Keith Kemp; sos-list@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [SOS-LIST] SOSCMD and CPU Usage
>
>Hi, Keith,
>
>Does the CPU stay pegged at 100% during the entire get? Does the get
>succeed?
>
>Actually, the SOS CLC is not an FTP client. It communicates with the SOS
>Server via TCP/IP and then the SOS Server communicates with the VSS
>database via the SourceSafe API, which uses Windows file sharing.
>
>Linda Bauer
>SourceGear
>Technical Support
>
>visit our support forum at
>http://support.sourcegear.com
>
>At 12:19 AM 3/13/2004, Keith Kemp wrote:
> >Well, odd that a program which is just a glorified FTP client would
require
> >all of the cpu. Client side.
> >
> >65MB 1300 files.
> >
> >P4 Mobile 2.4ghzm 1GB of ram. Windows XP
> >
> >New to me as I've just started using SOSCMD, I haven't had the GUI Client
>do
> >this on the same source tree.
> >
> >
> >Keith
> >
> >-----Original Message-----
> >From: Linda Bauer [mailto:Linda@xxxxxxxxxxxxxx]
> >Sent: Friday, March 12, 2004 1:06 PM
> >To: Keith Kemp; sos-list@xxxxxxxxxxxxxxxxxxx
> >Subject: Re: [SOS-LIST] SOSCMD and CPU Usage
> >
> >Hi, Keith,
> >
> >If there's CPU available, then the CLC will try to use it. Is this on the
> >client or server side?
> >
> >What size is this "get"? How many files and what size?
> >
> >What type processor, RAM, etc does the machine have?
> >
> >Is this a new problem? Does it happen for all gets?
> >
> >Linda Bauer
> >SourceGear
> >Technical Support
> >
> >visit our support forum at
> >http://support.sourcegear.com
> >
> >At 10:26 PM 3/11/2004, Keith Kemp wrote:
> > >Hello, I'm having trouble where SOSCMD is taking all my cpu is this
>normal?
> > >
> > >Here is my command:
> > >Binaries\Sos\soscmd.exe -soshome "C:\Program Files\SourceOffSite"
>-database
> > >"D:\CGI VSS\srcsafe.ini" -recursive -verbose -command GetProject
-project
> > >"$/CalPlan/Source/" -workdir Builds\1\SosTree\CalPlan\Source\
> > >
> > >_______________________________________________
> > >This is the SourceGear sos-list.
> > >Send postings to sos-list@xxxxxxxxxxxxxxxxxxxxx
> > >To unsubscribe or edit your mail options, go to:
> > >http://lists.sourcegear.com/cgi-bin/mailman/listinfo/sos-list
> > >and follow the instructions at the bottom of the page.
> >
> >
> >_______________________________________________
> >This is the SourceGear sos-list.
> >Send postings to sos-list@xxxxxxxxxxxxxxxxxxxxx
> >To unsubscribe or edit your mail options, go to:
> >http://lists.sourcegear.com/cgi-bin/mailman/listinfo/sos-list
> >and follow the instructions at the bottom of the page.
>
>
>_______________________________________________
>This is the SourceGear sos-list.
>Send postings to sos-list@xxxxxxxxxxxxxxxxxxxxx
>To unsubscribe or edit your mail options, go to:
>http://lists.sourcegear.com/cgi-bin/mailman/listinfo/sos-list
>and follow the instructions at the bottom of the page.
_______________________________________________
This is the SourceGear sos-list.
Send postings to sos-list@xxxxxxxxxxxxxxxxxxxxx
To unsubscribe or edit your mail options, go to:
http://lists.sourcegear.com/cgi-bin/mailman/listinfo/sos-list
and follow the instructions at the bottom of the page.
|