Stuart Barkley <[email protected]> writes: > Yes, just roll the log file (see responses to your question on that).
[Of course, qacct will only work for the entries left in `accounting' itself.] > When you get to proper accounting, these details are very important. > Being sure these edges don't duplicate or miss jobs and doing the > desired processing for jobs splitting reporting boundaries is another Why don't the intermediate accounting records cover that? Is it worth worrying about any real accuracy in accounting? Tyring to keep track of everything relevant, like system problems that clobber jobs, just doesn't seem worthwhile to me. > I may eventually do my own processing of the accounting records. There are assorted scripts floating around for doing that, including analyze.rb (?) in the distribution. Note that they need consideration of the configuration in general, such as the one slot/per node loosely integrated parallel jobs that were originally configured here... > At some point I may look again at the ARCo stuff in sge. The ARCo data > base may be useful to summarize data (including the extra data in the > reporting file). To me the java web interface looks very heavy and > would require a lot of work to get through a security review (multiple > web ports opened, new login methods, etc). I think everyone agrees it needs replacing, if something like it is required. > Another issue that we have is that we also run torque/Moab on another > cluster and I really want to normalize any formal reporting system to > include information from both clusters. Does Torque/Moab do something similar to GE or not? Probably not relevant to you, but for general info: That sort of thing came up on a UK National Grid Service list. I tried to explain that it wasn't straightforward for SGE, and it didn't seem that there could be a general recipe for incorporating arbitrary SGE configs. It wasn't clear to me whether that's because Torque isn't as flexible, or whether the same issues are really there too. > The accounting and reporting logs look like they can be easily > converted into a data set suitable for analysis with R. Usage > summaries by various parameters are probably pretty easy. Definitely doing using a general tool seems the Right Thing. I assume there are generic packages for producing pie charts, and other things management might understand, from database records. Does anyone have specific suggestions? _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
