| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
back in 2009.
"show modules" is the functional console command that will show currently loaded modules.
Addresses http://opensimulator.org/mantis/view.php?id=6730
|
| | |
| |
| |
| |
| |
| | |
add minor details to some log messages, rename a misleading local variable name.
No functional changes.
|
| | |
| |
| |
| |
| |
| |
| | |
transfer protocol into v2.
This stops OpenSimulator still trying to teleport the user if they hit cancel on the teleport screen or closed the viewer whilst the protocol was trying to create an agent on the remote region.
Ideally, the code may also attempt to tell the destination simulator that the agent should be removed (accounting for issues where the destination was not responding in the first place, etc.)
|
| |/ |
|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
all") to file OpenSimStats.log every 5 seconds.
This can currently only be activated with the console command "debug stats record start".
Off by default.
Records to file OpenSimStats.log for simulator and RobustStats.log for ROBUST
|
| | |
| |
| |
| | |
worker/iocp threadpool numbers
|
| |/
|
|
| |
estate bans also, and delete the obsolete config var.
|
| | |
|
| |
|
|
|
|
| |
not, either via config (SerializeOSDRequests in [Network]) or via the "debug comms set" console command.
For debug purposes to assess what impact this has on network response in a heavy test environment.
|
| |
|
|
|
|
| |
forget conditions.
I generally prefer this approach for regression tests because of the complexity of accounting for different threading conditions.
|
| |
|
|
| |
category - these are not things one needs to do in normal operation
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
position. That was a complete overkill that is unnecessary at this point.
|
| | |/
|/|
| |
| | |
with the console command "debug threadpool set"
|
| | |
| |
| |
| | |
If this is an issue, could change log4net config instead to allow re-enablement
|
| | |
| |
| |
| |
| |
| |
| | |
as well as max.
Make it clear that we only try to adjust max, and log at warn level if this fails.
Other minor logging cleanup.
|
| |\ \ |
|
| | | | |
|
| |/ /
| |
| |
| | |
thread numbers and immediate post config thread numbers
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
the fields get messed up because the transfer is async
|
| |/
|
|
|
|
| |
not hold.
Not yet in use.
|
| | |
|
| |
|
|
| |
foreigners if OutboundPermission is false
|
| |
|
|
| |
permissions by not allowing objects to be taken to inventory.
|
| |
|
|
| |
of sim freeze? -- HandleRequestImage in LLClientView is now sync, which means that it cannot take too long to complete. However, its execution path may end up in J2KDecoderModule.Decode, which is heavy and could stop the packet processing thread while it's at it.
|
| |
|
|
| |
section may not exist at all.
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
of linkset children while iterating through the list.
|
| | | |
| | |
| | |
| | |
| | | |
and processing routines in BulletSim.
Add linkset rebuild/conversion routine in BSLinkset.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
for each link in a linkset.
Extend BSLinksetConstraint to create and use BSLinkInfo with the default
static constraint.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
scripts as boxed integers rather than proper reference to a new LSLInteger.
This fixes an exception when using a registered integer constant in
a script.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
manually forced in a new [SimulationService] config setting.
This is for testing and debugging purposes to help determine whether a particular issue may be teleport related or not
"SIMULATION/0.2" (the newer teleport protocol) remains the default. If the source simulator only implements "SIMULATION/0.1" this will correctly allow fallback to the older protocol.
Specifying "SIMULATION/0.1" will force the older, less efficient protocol to always be used.
|
| | |/
|/|
| |
| | |
lock -- we should be "ok" (or, more "ok") now that we have increased the connection limit on the http library. But this is a sensitive part of the code, so it may need reverting.
|
| |/ |
|
| |
|
|
| |
InventoryAccessModules.RezObject() - structs are passed by value
|
| |
|
|
| |
multiple attachments changes (e.g. change outfit) are also throttled
|
| |\ |
|
| | |
| |
| |
| | |
regionhandle and saves it to to X,Y vars in the OpenSim.Framework.Location object was inverting the X and Y resulting in X and Y confusion. The test also used 256x256 in the uint,uint constructor so it was unable to determine if the X and Y components swapped. I don't expect much upheaval from this commit, not a lot of features were using the ulong Location object constructor. The database never stores the ulong regionhandle... the prims are loaded by region Guid. LLUDPServer used it to determine regions that it handled in a service definition where there was simply a X == X test which has the same logical result un-switched as it did switched. Again, thanks LibOMV for the regionhandle code.
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
| |
and ThrottlePer100PrimsRezzed in [Attachments] in config
This is an experimental setting to control cpu spikes when an attachment heavy avatar logs in or avatars with medium attachments lgoin simultaneously.
It inserts a ms sleep specified in terms of attachments prims after each rez when an avatar logs in.
Default is 0 (no throttling).
"debug attachments <level>" changes to "debug attachments log <level>" which controls logging. A logging level of 1 will show the throttling performed if applicable.
Also adds "debug attachments status" command to show current throttle and debug logging levels.
|
| |
|
|
|
|
|
|
| |
immediately if any data was sent, rather than waiting.
What I believe is happening is that on initial terrain send, this is done one packet at a time.
With WaitOne, the outbound loop has enough time to loop and wait again after the first packet before the second, leading to a slower send.
This approach instead does not wait if a packet was just sent but instead loops again, which appears to lead to a quicker send without losing the cpu benefit of not continually looping when there is no outbound data.
|
