[Beowulf] Time measurement
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Vincent Diepeveen diep at xs4all.nlWed Aug 3 09:10:07 PDT 2005
- Previous message: [Beowulf] RE: Beowulf Digest, Vol 16, Issue 35
- Next message: [Beowulf] Time measurement
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Always measure wall clock time of execution. That's IMHO the only thing that really counts and it includes all overhead. Take into account that at most clusters the wall clock time of node A is not the same like wall clock of node B. If you start a job at the head node and spawn it from there further to the rest of the cluster, what counts obviously is the time from when you started it, until it finished execution. Because in reality what matters is how quickly you did get the job done. Vincent At 08:13 AM 8/1/2005 -0700, ThanhVu H. Nguyen - Gmail wrote: >Hi, just wondering what the standard way of measure the execution time >? > >2 methods I thought about are: > >1) /usr/bin/time prog : this includes all the communcation, i/o , >loading overhead etc > >2) include start_time , end_time code in the program : this won't >include the communication , i/o , loading etc overhead. > >what method is usually used ? thanks > >tvn, > >ThanhVu H. Nguyen >_______________________________________________ >Beowulf mailing list, Beowulf at beowulf.org >To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf > >
- Previous message: [Beowulf] RE: Beowulf Digest, Vol 16, Issue 35
- Next message: [Beowulf] Time measurement
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
