| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
repetitive client requests for the same missing texture
* This is to maintain some visibility on the problem, since I removed the intentionally irritating log messages for this
|
|
the region server
* In theory, this should be a somewhat useless statistic since the user server will already have tried to use the inventory service to retrieve the avatar's skeleton. If this
fails, login is halted completely.
* Nonetheless I'm recording it anyway just to see whether it happens (yes, I'm too lazy to scan the logs...)
|
|
* If extra stats not sent to the viewer are available on an opensim server, they are now uniformly accessible using the 'show stats' command
|
|
Collectors - this seems more intuitive
|
|
(this took a while to run).
|
|
|
|
|
|
|
|
* Correct asset cache stats table heading
* Correct spelling mistake in AssetCache (thanks ChrisD!)
|
|
|
|
* This will show the packets waiting in each queue for each client logged into a region server
* These are displayed using 'show stats' on the region command line
* This is in pursuit of a memory leak.
* This will require a prebuild
|
|
If no scriptengine is specified then don't try to load any.
|
|
|
|
* You can type 'stats' at the REGION# prompt to get this information in grid or standalone mode
* Don't take these numbers as gospel yet, since for some reason textures displayed from inventory which require downloading from the server are being recorded as assets
rather than textures
* But I don't have any reason to believe they aren't broadly accurate.
* I've put these in so I can tell whether the high memory usage on regions is down to the asset/texture cache
* This will require a prebuild
* DEV: Only adds needed to be implemented since, as far as I can tell, assets cached are currently never released. For my part, seeing large cache memory numbers will
provoke me to think about doing something about this.
* DEV: Now switched to using a singleton to get the stats reporters rather than threading the object through various layers
* DEV: Will refactor the other server stats reporters to do this in one of the next commits
|
|
|
|
|
|
* Passing the stats collector through object chains is not ideal - this will change when more stats come in
* This change will need a prebuild
|
|
* The hooks are still plugged in too high at the asset server, but then next layer down is the database and this may be refactored soon.
* This change will requires a prebuild
|
|
|
|
* Typing 'stats' on the command line will given total number of successful logins today and yesterday
* A little bit more to come, probably
* Refactoring will follow next
|
