[GE users] Script for accounting(8) file analysis

Bernard Li bli at bcgsc.ca
Fri May 26 18:44:19 BST 2006


Good to know - now we just need to figure out how to distribute the
workload to analyze huge accounting files on a cluster ;-)

Thanks,

Bernard 

> -----Original Message-----
> From: Andreas.Haas at Sun.COM [mailto:Andreas.Haas at Sun.COM] 
> Sent: Friday, May 26, 2006 10:34
> To: users at gridengine.sunsource.net
> Subject: RE: [GE users] Script for accounting(8) file analysis
> 
> It must work both with 5.3 and 6.0. It depends only
> on the accouting file and it's format hasn't changed.
> 
> Andreas
> 
> On Fri, 26 May 2006, Bernard Li wrote:
> 
> > Hi Andreas:
> >
> > Does this only work with a specific version of SGE?
> >
> > Thanks!
> >
> > Bernard
> >
> > > -----Original Message-----
> > > From: Andreas.Haas at Sun.COM [mailto:Andreas.Haas at Sun.COM]
> > > Sent: Friday, May 26, 2006 4:56
> > > To: users at gridengine.sunsource.net; 
> announce at gridengine.sunsource.net
> > > Subject: [GE users] Script for accounting(8) file analysis
> > >
> > > Hi all,
> > >
> > > I added a Ruby script for accounting file analysis to
> > >
> > >    source/scripts
> > >
> > > directory of maintrunk and additionally made it available
> > > under
> > >
> > >    
> http://gridengine.sunsource.net/files/documents/7/82/analyze.rb.gz
> > >
> > > usage is
> > >
> > >       analyze.rb <options> accounting_file
> > >         -help
> > >         -r                                records table
> > >         -u                                users table
> > >         -h                                hosts table
> > >         -q                                queues table
> > >         -p                                projects table
> > >         -c                                categories table
> > >         -ts                               timesteps table
> > >         -ts_c                             categories per timestep
> > >         -ts_j                             jobs per timestep
> > >         -t "first"|<first> "last"|<last>  full analysis, but
> > > print these timesteps only
> > >
> > > the reason I worked on it is I needed job and category analysis on
> > > a timestep basis as provided by -ts -ts_c -ts_j and -t options.
> > >
> > > I think it is useful, even though it is certainly not perfect.
> > > E.g. rescheduled job are not orderly handled and there are
> > > certainly other insufficiencies.
> > >
> > > Give it a try, but be careful when using it with large accounting
> > > files.
> > >
> > > Regards,
> > > Andreas
> > >
> > > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> > > For additional commands, e-mail: 
> users-help at gridengine.sunsource.net
> > >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> > For additional commands, e-mail: users-help at gridengine.sunsource.net
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list