Netherlands
Same results here. Seems to work fine.
switch to a new logging framework (Log4Net) (1 Viewer)
- Thread starter Bavarian
- Start date
Same results here. Seems to work fine.
about log4net.. we really need this in tve3.5 as well as in tve3.5@mp2 
about logging performance, how does it work behinds the curtains ?
ideally it should be an "in memory queue" of log items.
then a threaded static logger class would pop those queued log items and commit them to disk, one at a time.
this would make calls to log very cheap performance wise.
so an encapsulation of log4net would be needed here.
I've already done similar work for an asynch mailer class at work.
send mail to queue and process it in a thread, then dispatch mails one at a time.
could easily be modded to take care of logging instead of mailing.
/gibman
about logging performance, how does it work behinds the curtains ?
ideally it should be an "in memory queue" of log items.
then a threaded static logger class would pop those queued log items and commit them to disk, one at a time.
this would make calls to log very cheap performance wise.
so an encapsulation of log4net would be needed here.
I've already done similar work for an asynch mailer class at work.
send mail to queue and process it in a thread, then dispatch mails one at a time.
could easily be modded to take care of logging instead of mailing.
/gibman
Last edited:
also when will we get log options in setuptv?
verbosity, rotation, max # logs to keep, ....
verbosity, rotation, max # logs to keep, ....
- Thread starter
- #14
It is all implemented in this branchalso when will we get log options in setuptv?
verbosity, rotation, max # logs to keep, ....
.One logger for all program's and compatible with the "old" implementation (=> no recompiling of the plugin's needed).
Last edited:
It is all implemented in this branchalso when will we get log options in setuptv?
verbosity, rotation, max # logs to keep, ....
One logger for all program's and compatible with the "old" implementation (=> no recompiling of the plugin's needed).
iloop, someone still needs to implement the log levels for every single logging call on TVE side for the verbose to work.
yeah feel free to do it
just remember there are 2 tve3.5 branches .. confusing right ?
@Sebastiii knows more about this
Once this is done I could goldplate it with the above mentioned threading model for performace goals.
/gibman
Isn't it quite big task to go thru every single log line in the TVE plugin and server and decide if they are info/warning/error?
If log4net is any sane logging framework it already should have the actual loggin in a separate thread and only the message queuing is done in the calling thread. Bavarian probably knows if this is the case.
So in that branch all the config options are availabe in the setuptv gui?It is all implemented in this branch
One logger for all program's and compatible with the "old" implementation (=> no recompiling of the plugin's needed).
in 1.3.0 the configfile has to be manually edited, right?