Message Logging - Logoffs

[jsquizz]

I am looking into slow response times, and I am seeing excessive activity being written to the system log.

The last time I saw this, per IBM, 65/226 records were causing extreme slowness in the system and eventually brought it down.

I am looking through log activity and I am wondering- can anyone think of a scenario when they needed to have logoff messages enabled? I an see logins, but not log offs.

[Justin Derrick]

System Log performance was improved in Content Manager OnDemand v9 and v9.5, so upgrading will help.

You'll want to consult your friendly neighbourhood DBA and ask them to help you improve insert performance.

The single best way to reduce the impact of query logging is to turn them off.

If you're also seeing a lot of login/logoff messages, I'd disable that.  If you're not seeing logoffs, then there's a chance that a web app is poorly written and abandoning connections, without closing them properly -- check into that as well.

-JD.

[jsquizz]

System Log performance was improved in Content Manager OnDemand v9 and v9.5, so upgrading will help.

You'll want to consult your friendly neighbourhood DBA and ask them to help you improve insert performance.

The single best way to reduce the impact of query logging is to turn them off.

If you're also seeing a lot of login/logoff messages, I'd disable that.  If you're not seeing logoffs, then there's a chance that a web app is poorly written and abandoning connections, without closing them properly -- check into that as well.

-JD.

I figured that was the case.

We are capturing mostly everything including logins and logoffs, but i am concerned about the 65/226... The last time this happened to me, when retirement statements would go out, the entire 3 server environment would crash.

10.1 is on the way!