Aurora 4x
C# Aurora => General Discussion => Topic started by: Froggiest1982 on December 02, 2020, 12:29:04 AM
-
So I am in a game almost 100 years with a save of roughly 25Mb DB.
After my first big ground combat (not even concluded yet) I am now noticing a 48Mb DB.
I then looked at what happened and it's all due to the insane amount of ground combat logs you get.
I am not sure if something was done already in there as I remember reading something that was actually just noticed that some events could get lost in the report and if I am not wrong the ground combat logs now are listed at the beginning and at the end there are all other events so that you could keep track which is great.
However, what about the DB size? I am concerned if I will get soon a 500Mb DB I am not sure how it's going to be handled performance-wise.
-
DB size definitely does matter for performance. Worst part is all your saves are in the same DB, so starting a brand new game will perform better the first time than on the 20th time. I didn't notice any real event-related slowdown until ~100 years and three ground invasions, two of which were heavily-defended homeworlds and so generated an absolute mountain of events.
Edit:
My current DB with that game I mentioned above is at ~78mb.
-
Worst part is all your saves are in the same DB, so starting a brand new game will perform better the first time than on the 20th time.
All my games are 1 DB as I do edit the DB from time to time and it is easier this way. Plus I noticed that even cancelling a game the DB size it's still bigger than it's supposed to be.
-
Ok so using SQLiteStudio I've done this so far for officer related events which works wonderfully:
delete from FCT_Gamelog
where (EventType = 129 or
EventType = 90 or
EventType = 291 or
EventType = 98 or
EventType = 42 or
EventType = 296 or
EventType = 292 or
EventType = 99 or
EventType = 256 or
EventType = 257) and
GameID = 38;
Warning: Your GameID might not be the same as mine so should be checked.
Warning: "EventType = 42" is not related to officers and instead refers to failed standing orders which I also wanted to remove.
The officer events refer to reassignments, promotions, health, retirement and the various events that fire when a specific type of officer is recruited.
You can check the thread that I posted this in as well for more info.
This should help you clear a lot of the combat stuff if you have a way to SQL query the DB.
-
Worst offender has got to be the Element vs GUC line. I got a fight against ~7000 tons of Precursors and my DB inflated by 5MB since last save.
Not too sure it's useful too, since there's also a recap where all the same units are lumped together, and another by formation.