Jump to content
  • Investigate moving the logging system to own thread

    • Status: Awaiting Dev Review
      Main Category: Core / Mangos Daemon
      Sub-Category: Code Enhancement
      Version: Unset Milestone: 22 Priority: Normal
      Implemented Version: Unset

    Talking to @H0zen the logging system can cause massive amounts of lag in-game to players.

    I have experience this with living world and a debug build, even with the log level set to 1 the core is still swarmed with log messages that are not seen.

    To smooth things out we need to move all console/log messages to their own thread. This will allow the core some room to breath and get on with actually serving the players in-game.

    Simple test of this is to load living world up in a debug core, even with logging disabled, you will experience a 2-3 minute wait getting onto just the character screen due to all the messages running in the background on the core taking up its process etc.

    h0zen has suggested that logged messages should be in their own thread and in a queue system of some kind. This issue is to investigate this further and see what can be done to improve logging stability with lots of core actions happening.

    User Feedback

    Recommended Comments

    There are no comments to display.

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use