took about 100 seconds to complete "scm status"?
Hi All,
i have a workspace loaded into my local sandbox with about 200,000 files contained, each time i issued a "scm status" command, it took about 100 seconds to complete, is this normal?
RTC Version: 3.0.1
RTC AP Server: 4 core CPU, 8G RAM, RedHat Enterprise 5
RTC DB Server: 4 core CPU, 8G RAM, Oracle 11g, RedHat Enterprise 5
RTC Client: 4 core CPU, 6G RAM, Ubuntu 10.04
Regards,
Makson
i have a workspace loaded into my local sandbox with about 200,000 files contained, each time i issued a "scm status" command, it took about 100 seconds to complete, is this normal?
RTC Version: 3.0.1
RTC AP Server: 4 core CPU, 8G RAM, RedHat Enterprise 5
RTC DB Server: 4 core CPU, 8G RAM, Oracle 11g, RedHat Enterprise 5
RTC Client: 4 core CPU, 6G RAM, Ubuntu 10.04
Regards,
Makson
2 answers
'scm status' does couple of things... a) it contacts the repository to check if there are any new changes and b) it scans the local file system to detect if there were any updates.
Scanning the local file system usually takes some time and if you didn't intend to do that you can run scm status with -n option.
I would also recommend using 'lscm' rather than 'scm' as there is jvm startup cost involved on every launch of 'scm'. Using 'lscm' you will incur the cost once and subsequent execution of commands will be faster.
Also, if you have multiple components, stepping into the component directory and running 'lscm status' will only refresh that component.
Scanning the local file system usually takes some time and if you didn't intend to do that you can run scm status with -n option.
I would also recommend using 'lscm' rather than 'scm' as there is jvm startup cost involved on every launch of 'scm'. Using 'lscm' you will incur the cost once and subsequent execution of commands will be faster.
Also, if you have multiple components, stepping into the component directory and running 'lscm status' will only refresh that component.
Hi All,
i have a workspace loaded into my local sandbox with about 200,000 files contained, each time i issued a "scm status" command, it took about 100 seconds to complete, is this normal?
RTC Version: 3.0.1
RTC AP Server: 4 core CPU, 8G RAM, RedHat Enterprise 5
RTC DB Server: 4 core CPU, 8G RAM, Oracle 11g, RedHat Enterprise 5
RTC Client: 4 core CPU, 6G RAM, Ubuntu 10.04
Regards,
Makson
Hi,
thanks for your reply, i also tired the lscm command, took the same time too.
i am thinking that if there is a daemon to monitor the local sandbox modification and log it, so that everytime we run the "scm status", it will check local database instead of doing full scan to sandbox.
Regards,
Makson
thanks for your reply, i also tired the lscm command, took the same time too.
i am thinking that if there is a daemon to monitor the local sandbox modification and log it, so that everytime we run the "scm status", it will check local database instead of doing full scan to sandbox.
Regards,
Makson
'scm status' does couple of things... a) it contacts the repository to check if there are any new changes and b) it scans the local file system to detect if there were any updates.
Scanning the local file system usually takes some time and if you didn't intend to do that you can run scm status with -n option.
I would also recommend using 'lscm' rather than 'scm' as there is jvm startup cost involved on every launch of 'scm'. Using 'lscm' you will incur the cost once and subsequent execution of commands will be faster.
Also, if you have multiple components, stepping into the component directory and running 'lscm status' will only refresh that component.
Hi All,
i have a workspace loaded into my local sandbox with about 200,000 files contained, each time i issued a "scm status" command, it took about 100 seconds to complete, is this normal?
RTC Version: 3.0.1
RTC AP Server: 4 core CPU, 8G RAM, RedHat Enterprise 5
RTC DB Server: 4 core CPU, 8G RAM, Oracle 11g, RedHat Enterprise 5
RTC Client: 4 core CPU, 6G RAM, Ubuntu 10.04
Regards,
Makson