Jump to content
  • entries
    8
  • comments
    3
  • views
    2,280

CHAPTER 2: Papyrus Log


GenioMaestro

667 views

Another stupid point is about the SPAM IN THE LOG because not have any relation whit the game performance.
You can run yours own test for verify it. The game run exactly equal with the same latency and performance with the log enabled or disabled.
Disable the log in Skyrim.ini not mean the game not execute the log line. Simply not write it to the log file but the debug lines are efectively executed.
I can execute ALL my tests with ALL the debugging options enabled in Skyrim.ini and I do not see any difference.
In some cases i get a log file of more than 512 MB and Notepad++ say me the file is too big for open it.
My test can generate thousand and thousand of log lines per second and is a very good demostration.
If you enable trace in your Skyrim.ini and run my test you can get a Papyrus.0.log of megas and megas and that not make any diference for the game.
The SPAM IN THE LOG can not cause any problem to the game and can not slow down the game or increase the latency or the response time.

 

This is because the log of Skyrim is a BUFFERED file. When the game wants write some to the log really are writing it in memory.
The work of write the file to the hard disk is made by the operating system and is NOT made by the game.
Normally, a BUFFERED file is managed in chunks of 4 kb and write 4kb of data in the disk is a stupid operation for the machine.
This buffer of 4 kb can be dinamically increased, but only in the operating system side, to 64 kb if necesary.
In this way, when the game need put a lot of lines in the log the operating system dinamically increase the internal buffer size for reduce the hard disk operation.
And for that reason, the SPAM IN THE LOG can not give any problem to the game.

0 Comments


Recommended Comments

There are no comments to display.

×
×
  • 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. For more information, see our Privacy Policy & Terms of Use