Just logged in, ran a mission OK, flipped a hex. Looks like some ghosts on there tho, I'm guessing network hiccup, when exactly did the trouble start? (I backed up the db at 11 AM AST while live - which might have caused troubles, the sql db is up to 1.2 MB now [battle logging and created ai filling it])
The thread count continues to steadily rise... must be due to the ghosted accounts... I'll reboot it now so its fresh for tonight, I'm hoping to get 25 on still to see what happens. (4 days without a reboot - not bad I guess)
Seemed to be about 78 threads that would not close when I tried to shutdown the kit using its menu, its thread and memory use (~63MB mem) only stopped when I closed the window. Its thread count and memory use are back down to normal after a reboot (~14 threads ~ 18MB mem). If I see the same process happens faster with 25 players on in a short time (over and above threads normally created by active players), as opposed to with just a few on over 4 days, then I can take a hard look at the kit to find the cause. (I do expect some mild improvement with this build however, if so I'll continue my edits along the same lines)
The "normal" thread count hovers around the number of tables in the SQL db with no players on, this event and observations leads me to believe I'm on the right track, I can explain better later... its adding up... (I'd like to study the flatfile in the same way for comparison sometime)
Topic: Bonk we might have broke it (Read 923 times)