>In G2 real logfile you have the size of information which has been
>transfered (like 200000, etc). I was thinking using that to guess how
>long the guy stayed connected, but with surestream it gets really
>difficult.
Apache and most HTTP servers allow you to log processing times, and Analog
has a PROCTIME report. Maybe your G2 server has something similar?
Otherwise, you may chart bytes against "typical" user modems' baud rates.
To keep in touch with reality, I'd also suggest considering an efficiency
parameter, usually 80-90% in off-peak hours and from 60% to 75% during peak
hours (though it could even be worse).
that is:
1MBytes / 28.8baud * 0,9 = 262+ seconds (4 minutes, 22 seconds and dimes)
You'd want a reasonable statistics on modem speed distribution (what
percent of users have which kind of modem), of course.
I'd include 56K, 33.6, 28.8 and 14.4 modems, and compute each column at
least twice, for peak and off-peak efficiency. This would give you a lot of
columns and chatrs, but I think it's also the best way to insure you get a
rasonable picture of what reality could be.
The table and charts you'd get would still not be God's own word on stone,
but it may still be better than nothing.
I'm afraid you may not be able to do the "otherwise" part with analog,
unless you tried to trick it into thinking it's all PROCTIME data. But
then, you may be better off with a spreadsheet for this.
Hope this helps.
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
