Opened 8 years ago
Last modified 3 years ago
#3834 new enhancement
Find a way to shrink or split OOS logs — at Version 2
Reported by: | sanderd17 | Owned by: | |
---|---|---|---|
Priority: | Should Have | Milestone: | Backlog |
Component: | Core engine | Keywords: | patch |
Cc: | Patch: |
Description (last modified by )
OOS logs are getting too big to work with.
Logs of long games (when there are a big number of units) can't be opened with all text editors anymore, and there's certainly a problem with certain diff tools (like meld).
Some things could be optimised:
TechnologyTemplateManager shouldn't serialise any data (it can always load the techs from disk when rejoining). r18100- SerializeVector is very ineffecient; it stores the name of the array with every element, which results f.e. in a lot of lines like
los state: 0 los state: 0 los state: 0 ....
Next to optimising the OOS log, it could also be split. F.e. one log for the SYSTEM_ENTITY (which currently takes up 25% of the entire log), and then f.e. a log per 1000 or 2000 entities
Change History (3)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Description: | modified (diff) |
---|
by , 8 years ago
Attachment: | smallerOOSlog.diff added |
---|
Note:
See TracTickets
for help on using tickets.
In 18100: