Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
First of all, you seem somewhat reluctant to let us know what program you're trying to optimize--why is that? At least, you could have told us what it does--all we know is that it connects to the net and prints stuff on stdout. Does it write to the disk as well? Is it a streaming ascii-art video client? Is it rsync? Also, what language is the program you're optimizing written in?
Anyways, here's my suggestion: compile the program with profiling enabled and ask your profiler what's taking your program so damn long.
Sorry about that. I wanted to avoid publicly badmouthing Clearcase *oh well*.
It seems it's not limited to any one application, although Clearcase is the most visible as it's the most widely used. The scripts that automate the user interaction are written in Perl and call clearcase commands, ie - checkout, rebase, deliver (and perl's times function returns only a few seconds for parent/child system times, neglibile at this point, while the overall start->finish time can be drastically higher. One operation takes around 30 seconds of system time, but the overall user experience is more than 15 minutes).
My guess, and I'm not too familiar with this, is that it's a combination of network connectivity, (although the pipe was tested at 32MB/s), and system I/O.
A colleague mentioned to me using sar and io-stat to debug the I/O...but I'm not familiar with interpreting the results.
Basically, I'm more curious in analyzing the I/O, as several tools unrelated to clearcase seem to have this issue. General overall performance seems slow.
try timing it with the bash builtin `time', to get system, user and wall-clock time, and see if anything looks odd. Also, for disk I/O, having a look at hdparm may be a good idea. Otherwise, I'm pretty much out of ideas, having never worked with clearcase, and "general overall performance" being a bit... big to work with.
You could start by writing a short Perl prog to run on the server and check cpu & disk I/O perf. If no problem, implies network issue, in which case, run the same prog from your desktop against server.
A v useful perl module is: http://search.cpan.org/~bloonix/Linu.../Statistics.pm
Also, just looking at top should give you an idea as to whether it's local to the server or not.