Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007781opensim[GRID] Hypergridpublic2015-12-13 10:142015-12-13 10:16
Reporteraiaustin 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformPCOSWindowsOS Version10
Product Versionmaster (dev code) 
Target Versionmaster (dev code)Fixed in Version 
Summary0007781: Hypergrid handing of GetRegionByPosition - possible unnecessary work for adjacent region checks after hypergrid jump
DescriptionI note messages of the form "[GRID SERVICE]:GetRegionByPosition" in the
OpenSim.exe console logs when moving between two grids using Hypergrid?
The logs looks like a lot of unnecessary adjacent region checking is
going on and maybe we are doing unnecessary work. Is this an issue
worth reporting on Mantis?


Using the latest 0.9.0.0 dev master... I am moving between a very simple
test grid with one region located at (5500,5500) and the AiLand grid which
has about 10 regions clustered around (6400,6400).

All regions are standard 256x256 sized ones and always have been on both
grids.

When I do a HG teleport to AiLand it seems to try this on the source grid
OpenSim.exe console... "GetRegionByPosition. Did not find region in
database. Pos=<26730,0>". Where does the <26730,0> come from? On a second
attempt later from exactly the same single region and X,Y,Z point it used a
different number Pos=<18470,0>. It would be useful to know what these
numbers mean and where they come from, as well as why they different on HG
jumps from exactly the same place.

Also, coming back home to the single region on the home grid it attempts a
lot of "GetRegionByPosition" lookups. Eah indicates "Did not find region in
database. Pos=<6399,6399>" and that seems to be tried for region X,Y
positions up to 2 in each direction all around the OTHER grid.. but these do
not relate to the home grid at all. Why does it try to look up regions that
relate to the foreign grid after a return home? This sounds like its doing
unnecessary work.

E.g. I see this in the OpenSim.exe console log after I have teleported home
from AiLand back onto the single region home grid. That region is at
<5500,5500>. The AiLand grid and region at <6400,6400> I just teleported
away form had regions that would previously have been in view (512m view
distance) before the teleport... but these messages all occur on the HOME
grid after the jump back home...

09:48:33 - [GRID SERVICE]: GetRegionByPosition. Did not find region in
database. Pos=<6400,6400>
09:48:33 - [LOCAL GRID SERVICE CONNECTOR]: GetRegionByPosition.
Region not found by grid service. Pos=<6400,6400>
09:48:33 - [GRID SERVICE]: GetRegionByPosition. Did not find region in
database. Pos=<6400,6399>
09:48:33 - [LOCAL GRID SERVICE CONNECTOR]: GetRegionByPosition.
Region not found by grid service. Pos=<6400,6399>
09:48:33 - [GRID SERVICE]: GetRegionByPosition. Did not find region in
database. Pos=<6400,6401>
09:48:33 - [LOCAL GRID SERVICE CONNECTOR]: GetRegionByPosition.
Region not found by grid service. Pos=<6400,6401>
09:48:33 - [GRID SERVICE]: GetRegionByPosition. Did not find region in
database. Pos=<6399,6399>
09:48:34 - [LOCAL GRID SERVICE CONNECTOR]: GetRegionByPosition.
Region not found by grid service. Pos=<6399,6399>
09:48:34 - [GRID SERVICE]: GetRegionByPosition. Did not find region in
database. Pos=<6402,6400>
09:48:34 - [LOCAL GRID SERVICE CONNECTOR]: GetRegionByPosition.
Region not found by grid service. Pos=<6402,6400>
09:48:34 - [GRID SERVICE]: GetRegionByPosition. Did not find region in
database. Pos=<6398,6401>
09:48:34 - [LOCAL GRID SERVICE CONNECTOR]: GetRegionByPosition.
Region not found by grid service. Pos=<6398,6401>
09:48:34 - [GRID SERVICE]: GetRegionByPosition. Did not find region in
database. Pos=<6398,6398>
09:48:34 - [LOCAL GRID SERVICE CONNECTOR]: GetRegionByPosition.
Region not found by grid service. Pos=<6398,6398>
09:48:34 - [GRID SERVICE]: GetRegionByPosition. Did not find region in
database. Pos=<6401,6400>
09:48:34 - [LOCAL GRID SERVICE CONNECTOR]: GetRegionByPosition.
Region not found by grid service. Pos=<6401,6400>
TagsNo tags attached.
Git Revision or version numberopensim-0.9.0-166-g5c39d97
Run Mode Grid (Multiple Regions per Sim)
Physics EngineBulletSim
Environment.NET / Windows64
Mono VersionNone
ViewerFirestorm 4.7.5
Attached Files

- Relationships

-  Notes
(0029813)
aiaustin (developer)
2015-12-13 10:15

Ubit reported on IRC...

The locations <x,0> are HG linked regions, i.e. other grid regions placed our map on a virtual position. It keeps getting new numbers even when we would expect reuse (considering this is per region)

Sure something isn't right on HG, so the need for the spam :(

- Issue History
Date Modified Username Field Change
2015-12-13 10:14 aiaustin New Issue
2015-12-13 10:15 aiaustin Note Added: 0029813
2015-12-13 10:16 aiaustin Description Updated View Revisions


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker