That's very odd because the output of "show stats" is extremely similar to diagnostics. Diagnostics does log some extra
information, but nothing which should cause this kind of issue.
To be honest, this should be configurable but I am really strapped for time right now. It would be very handy if you
could try disabling this manually by commenting out the lines (80-81)
m_periodicDiagnosticsTimer.Elapsed += new
ElapsedEventHandler(LogDiagnostics);
m_periodicDiagnosticsTimer.Enabled = true;
in the BaseOpenSimServer() constructor in BaseOpenSimServer.cs and see if that
makes a difference.
Could this possibly be some issue with writing anything to console? Do you have logging settings which would otherwise
write data?
On 31/07/13 23:36, Chris M wrote:
Hi Justin, I have observed this on several different systems with different
databases and varying amounts of scripted
objects and regions (ranging from very few to fairly populated). I see very
little CPU use for OpenSim when this is
happening but yet the systems hang up entirely for a while as it's doing it
(appx 30 seconds to 1 minute) and only when
the automated diagnostics starts to output its information to the console. This
started back sometime midway through
development of 0.7.5 (if I remember correctly) and then it went away for for a
little while after some commits after it,
then reappeared again. So I'm not exactly sure when it first started. I would
think that git bisect would take a good
while to do to track it down since I would have to wait an hour per test for
diagnostics to show up... the show stats
command doesn't seem to invoke this behavior.
Hi Dahlia, I hadn't thought to check my HDD light as it was happening (due to
my desk layout it's a bit difficult to see
the light from where I sit; so I had never just casually glanced over to look.)
I will keep an eye out for the HDD light
when it does it again though.
On 7/31/2013 4:14 PM, Justin Clark-Casey wrote:
I'm extremely surprised to hear this - no significant CPU operations are
involved in printing this information. Are
you absolutely sure that some other timed script isn't running at the same
time? Also, when did this problem start?
On 31/07/13 01:00, Chris M wrote:
Hello all,
I was wondering if it is possible to configure how often the automated
simulator diagnostics is ran, and if so, where
at?
It seems like every hour when the diagnostics is ran it results in hanging my
entire system up for about 30 - 45 seconds
which results in a variety of interesting things such as the viewer hanging up
entirely for that duration, music stops
playing if listening to music via external media player, other programs hang
up, etc. It also tends to translate to lag
for other people connected to my setup for about that long as well.
I know the ideal situation would be to run OpenSim on a system dedicated to
that; but right now I have no choice but to
run it on the system that I do all my other daily things on. So I would like to
configure diagnostics to run every
say... 8 hours or so? It would make the system hangs a bit more bearable :)
If it's not configurable externally I'm willing to stick my head into the
source code and change it manually there if
need be; if I could be pointed to the file and location in the code to change
it... It's just driving me insane lol.
Thanks!
--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
