> -----Original Message----- > L.C. (Laurentiu C. Badea) > Sent: Wednesday, December 15, 2004 3:27 AM > > >>5) "post-request" for logging and cleanup. Ideally this would be > >>called after the reply has been sent (hence the name) because there > >>is no point to make the client wait while we prepare the logs. > > > > > > That's not a bad idea, but I'm not sure where it would be useful. > > Do you have examples? > > It's mainly a performance improvement. Under high load, to > maintain the > fastest response time, the extra time taken to (write log > file + detail + sql) > becomes significant, and since we already have all the > response data, we might > as well send it before we do that. > > This opens up the possibility of moving the logging overhead > into a separate > thread with lower priority, that does not have to be > synchronized to the > request handlers any more. This should give you a performance > boost at the > cost of not getting real-time logs under load.
I feel uncomfortable with something happening with logging occured. When talking about auth this might be ok, for acct it is definitely not. My opinion is: waht couldn't get logged shouldn't happen and when replying before *trying* to log this cannot be garuateed. performance shouldn't affect interity.. just my two cents ;) Michael - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
