| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
closed on teleport, don't unnecessarily resend all avatar and object data about that region.
|
| |
|
|
|
|
| |
neighbour) don't resend all the initial avatar and object data again.
This is unnecessary since it has been received (and data continues to be received) in the existing child connection.
|
| |
|
|
|
| |
This adds the "show stats", "stats record", etc. commands and information on available Threadpool threads, etc.
It also adds the Watchdog which logs warnings if time between executions is unexpectedly large.
|
| |
|
|
|
|
|
|
| |
reprioritization distance to be changed on the fly.
This governs when child agent position changes are sent to neighbouring regions.
Corresponding config parameter is ChildReprioritizationDistance in [InterestManagement] in OpenSim.ini
For test purposes.
|
| |
|
|
|
|
|
| |
a huge number.
A stop gap solution - a better one may be to improve stats display on simulator-side.
Caps information is still accessible via the "show caps stats by user" and "show caps stats by cap" commands
|
| |
|
|
|
| |
For each service endpoint (e.g. posts to the xinventory service), a stat is available which shows the number of requests received and moving average per second
The full name is "service.<http-method>:<path>.requests (e.g. service.POST:/xinventory.requests)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
queues")"
Fixes http://opensimulator.org/mantis/view.php?id=7280
It can't be done this way because the stats data needs to show up on the console at all log levels, not just debug.
But this means setting it to log at fatal, which is not appropriate for this stuff in the log.
I understand the desire but this has to be done some other way, perhaps by (yet another) config parameter.
Also, this was already being done with the ClientStatsReport but that also should be done in another way, I think.
This reverts commit 5d534127663899cd5592c865b1d00855fce25854.
|
| |
|
|
|
|
| |
places.
Easier to read and analyze, and probably still too much detail (1 dp would probably be fine)
|
| |
|
|
|
|
| |
Despite the comments in the code, it appears that the issue where the .NET performance counter was wrongly idle time time on Mono was fixed in 2009.
https://bugzilla.novell.com/show_bug.cgi?id=468625
Which means that the workaround is no longer necessary and produces bad results instead.
|
| | |
|
| |
|
|
| |
the entire request and response)
|
| |
|
|
| |
is being throttled due to past poor performance.
|
| | |
|
| |
|
|
| |
"Queue threadfunc" for a particular thread then don't log "Run threadfunc" or "End threadfunc" for that thread either.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
has already been registered without needing to also run it
|
| |
|
|
|
|
|
|
| |
As per http://msdn.microsoft.com/en-us/library/system.random%28v=vs.100%29.aspx, the .NET Random class is not thread-safe.
If called by multiple threads at once, methods may return 0.
Except for llRand(), other OpenSimulator code did not lock before calling a shared Random instance.
This commit adds a ThreadSafeRandom class that extends Random but does internal locking so that it is thread-safe.
This change is invisible to existing callers and the explicit locking in the llFrand() implementation is now redundant.
|
| | |
|
| |
|
|
|
|
| |
In commit e6080a38 (Wed Mar 19 00:29:36 2014) I renamed this from "debug stats record start|stop"
Unfortunately, I didn't do this fully so before this commit "stats record start|stop" will report a usage failure with the old debug text.
Unfortunately this is in the 0.8 release. The workaround is to repeat the last command twice (e.g. "stats record start start")
|
| |
|
|
|
|
| |
shutdown.
Adds regression test for this case.
|
| | |
|
| | |
|
| |
|
|
|
| |
that simulator statistics is output to the console. Setting to zero turns
stats logging off.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Specifically, StoreEstateSettings was not being used anywhere; instead EstatSetting.Save was being called, but that method is a trigger to the DB-layer code directly, which, besides being wrong, was making it impossible to replace the service with a remote connector.
Also added more packing/unpacking code.
|
| |
|
|
|
|
| |
erroneous information.
Also, added conversion of EstateSettings from/to key-value pairs in preparation for robust net work connectors.
|
| |
|
|
| |
required. This preserves API compatibility for external modules using this function.
|
| |
|
|
|
|
| |
bitmap generation in WorldMapModule throw an exception on next startup.
This commit replaces the hardcoded region sizes in WorldMapModule.GenerateOverlay() with numbers pulled from m_scene.RegionInfo
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
than on every single log.
Compiling every time is unnecessary since Regex is thread-safe.
|
| | |
| |
| |
| | |
RegexOptions.SingleLine
|
| |/ |
|
| |
|
|
| |
because everything has worked so far, but it's the right thing to do.
|
| | |
|
| |
|
|
|
|
|
|
| |
SynchronousRestObjectRequester.MakeRequest() calls with no timeout specified use the default HttpWebRequest timeout as previously.
I mistakenly thought that that default request timeout was inifite rather than 100 seconds, restoring previously behaviour.
As per http://msdn.microsoft.com/en-us/library/system.net.httpwebrequest.timeout%28v=vs.100%29.aspx
Relates to http://opensimulator.org/mantis/view.php?id=7165
|
| |
|
|
|
|
| |
SynchronousRestObjectRequester.MakeRequest() methods with proper Timeout.Infinite (-1) instead.
Triggered by recent faf9ba53 though this was wrong in the code before, it's just that we didn't actually try to set the timeout given.
|
| | |
|
| |
|
|
|
|
|
| |
verb, string requestUrl, TRequest obj, int pTimeout, int maxConnections) actually set timeout on WebRequest if given.
Previously, we were doing nothing with this parameter.
No effect on current code since none of the 6 callers attempt to use the timeout.
|
| |
|
|
| |
Folder Type 8. (Previously we had used Folder Type -1 in one place, and LLClientView didn't even bother changing Folder Type 100 to anything else.)
|
| |
|
|
| |
was missing in TryParseConsole2DVector(). xbuild still compiles.
|
| | |
|
| |
|
|
|
|
| |
region co-ordinate.
For debug purposes.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Per http://wiki.secondlife.com/wiki/Tips_for_Creating_Heightfields_and_Details_on_Terrain_RAW_Files#Notes_for_Creating_Height_Field_Maps_for_Second_Life
terrain heights up to 508 are possible on the LL grid (and were available on previous releases of OpenSimulator).
The obvious way to allow both this and equivalent -z values, is to rewiden the internal terrain height storage from short to int.
The memory tradeoff is most noticeable on the maximum 8192x8192 var region (equiv to 1024 normal regions), where it adds 128mb to resident use (128k on a normal region)
This is still better than the double used in previous releases.
This does not affect physics or data storage since they already use float and double respectively.
This may not be the final solution if we actually want to sacrifice -z, >327 or something else.
Relates to http://opensimulator.org/mantis/view.php?id=7076
|
| |
|
|
|
|
| |
config option, LogOverloads, to log when a thread pool overload occurs.
This option defaults to "True" because the logging data is useful for
diagnosing threading issues.
|
