Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #12854

Re: Logging problem

From Martin Gregorie <martin@address-in-sig.invalid>
Newsgroups comp.lang.java.programmer
Subject Re: Logging problem
Date 2012-03-10 20:23 +0000
Organization UK Free Software Network
Message-ID <jjgd8p$qdr$1@localhost.localdomain> (permalink)
References (5 earlier) <XnsA011A83F55743jpnasty@94.75.214.39> <11598111.961.1331330200504.JavaMail.geo-discussion-forums@pbcr5> <XnsA011B6A6E1BB4jpnasty@94.75.214.39> <jjfpq8$hr3$1@localhost.localdomain> <JML6r.32762$L12.9349@newsfe23.iad>

Show all headers | View raw


On Sat, 10 Mar 2012 13:00:25 -0400, Arved Sandstrom wrote:

> Come, come, Martin, desktop Windows isn't quite so bad.
>
I wasn't saying it was - just that The Microsoft Way tends not to use 
logs to the extent that *NIXen do. 

I admit its been quite a while since I've used Windows in developer mode, 
but about the only place I can remember seeing good logging was from ODBC, 
and only then if it was configured on. The ODBC log entries weren't 
timestamped, but were pretty good in all other respects.[*]

OTOH every *NIX system I've used produces timestamped logs and has a 
mechanism for changing logfiles and keeping the number kept under 
control. IOW I've never see a log under Windows that let me see what had 
happened at about 02:30:15 last Wednesday but all Unices support that 
sort of thing.
 
Hey, Novice - this example below is a good example of the unexpected 
places where a decent log can come in useful.

[*] I was using the ODBC logs to help me tune one of the more 
incompetently written databases I've seen. No adequate application 
documentation of course! So, I was reduced to exercising every function 
of the application with ODBC logging turned on and then working through 
the log to work out what indexes and table storage strategies were needed 
to make the database perform: AKA doing a traditional access path 
frequency analysis after the app had gone live and promptly slowed to a 
crawl. You really can't expect a join on 25,000 accounts to be fast if 
there are no indexes to support it, though somebody had done exactly 
that. And, of course the problem didn't show up during development, which 
had populated the test database with the traditional handful of accounts: 
when each table occupies no more than one or two disk blocks all queries 
are quick.


-- 
martin@   | Martin Gregorie
gregorie. | Essex, UK
org       |

Back to comp.lang.java.programmer | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Logging problem Novice <novice@example..com> - 2012-03-08 19:38 +0000
  Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-08 14:48 -0500
    Re: Logging problem Novice <novice@example..com> - 2012-03-08 20:06 +0000
      Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-08 15:38 -0500
        Re: Logging problem Martin Gregorie <martin@address-in-sig.invalid> - 2012-03-08 22:02 +0000
      Re: Logging problem Patricia Shanahan <pats@acm.org> - 2012-03-08 14:53 -0800
        Re: Logging problem markspace <-@.> - 2012-03-08 15:20 -0800
          Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-08 19:48 -0500
            Re: Logging problem Patricia Shanahan <pats@acm.org> - 2012-03-08 17:17 -0800
              Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-08 20:55 -0500
                Re: Logging problem markspace <-@.> - 2012-03-08 18:01 -0800
                Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-08 21:19 -0500
      Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-08 20:56 -0500
  Re: Logging problem markspace <-@.> - 2012-03-08 14:18 -0800
    Re: Logging problem Novice <novice@example..com> - 2012-03-09 01:53 +0000
      Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-08 20:59 -0500
      Re: Logging problem Novice <novice@example..com> - 2012-03-09 05:36 +0000
        Re: Logging problem Patricia Shanahan <pats@acm.org> - 2012-03-09 06:27 -0800
        Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-09 12:31 -0500
          Re: Logging problem Novice <novice@example..com> - 2012-03-09 18:57 +0000
            Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-09 14:26 -0500
        Re: Logging problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2012-03-09 15:59 -0400
          Re: Logging problem Novice <novice@example..com> - 2012-03-09 21:32 +0000
            Re: Logging problem Lew <lewbloch@gmail.com> - 2012-03-09 13:56 -0800
              Re: Logging problem Novice <novice@example..com> - 2012-03-09 22:57 +0000
                Re: Logging problem Martin Gregorie <martin@address-in-sig.invalid> - 2012-03-10 14:51 +0000
                Re: Logging problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2012-03-10 13:00 -0400
                Re: Logging problem Lew <noone@lewscanon.com> - 2012-03-10 10:04 -0800
                Re: Logging problem Martin Gregorie <martin@address-in-sig.invalid> - 2012-03-10 20:23 +0000
                Re: Logging problem Lew <noone@lewscanon.com> - 2012-03-10 07:56 -0800
                Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-10 12:05 -0500
                Re: Logging problem Lew <noone@lewscanon.com> - 2012-03-10 10:10 -0800
                Re: Logging problem Arne Vajhøj <arne@vajhoej.dk> - 2012-03-12 16:13 -0400
                Re: Logging problem Novice <novice@example..com> - 2012-03-10 20:10 +0000
            Re: Logging problem Arved Sandstrom <asandstrom3minus1@eastlink.ca> - 2012-03-09 19:15 -0400
              Re: Logging problem Novice <novice@example..com> - 2012-03-10 01:59 +0000

csiph-web