Something about erlang log framework -


we have try use lager our log framework. meet problem.

  1. lager may lost date, have saw source code of lager, think reason gen_event notify async call, doesn't guarantee message receiving.

  2. lager performance not enough. guess because of lager's file backend written erlang. doesn't have performance.

so, think log framework written c, , capsulated erlang may choice.

do know erlang framework meet requirements?

  1. lager create event named 'lager_event' in application.

  2. for every backend, there 1 gen_event process handle it. therefore if many process generating messages @ same time, log of course lost @ 1 specific time. not related language use.

sugguest: 1. control log quantity. 2. rid of erlang's event system , create jobs(tasks)'s subsystem (multi processes) handle log.


Comments

Popular posts from this blog

java - Intellij Synchronizing output directories .. -

git - Initial Commit: "fatal: could not create leading directories of ..." -