[Swift-devel] Swift Performance Data

[Mihael Hategan]

On Mon, 2007-06-25 at 13:54 +0000, Ben Clifford wrote:
> On Mon, 25 Jun 2007, Mihael Hategan wrote:
> 
> > Another difficulty is that if we want meaningful things in that 
> > particular format, the whole software stack needs to be changed 
> > (including cog and jglobus and perhaps other things). This sounds a bit 
> > difficult, especially considering the fact that the information is 
> > there, but the format is not. I'd rather write a few simple parsers than 
> > try to change all logging messages everywhere.
> 
> 'a few simple parsers' is not necessarily 'simple'.

It's relatively simple. The python tool that is an adaptation of Jens'
shows that it can be done relatively easy. I would worry more about
Swift producing sufficient information and about how that information is
represented. That seems harder to me.

> 
> changing logging messages in code everywhere definitely isn't, though.
> 
> if there is going to be more than one analysis tool, converting log files 
> to a common format somewhere in between generating application and 
> analysing application might be a good idea, and not massively different 
> from defining a language level API to abstract out log file format 
> differences.

This is similar to code generation vs. abstraction (or interpretation
vs. compilation). There can be:
1. An api to access the logs in structured ways
2. A log translator
3. An adaptor plugged in at the log4j (or whatever logging library)
level that does the translation dynamically (at the expense of
performance).

Mihael

>