GetRegionByPosition - possible unnecessary work for adjacent region checks after hypergrid jump?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

GetRegionByPosition - possible unnecessary work for adjacent region checks after hypergrid jump?

Ai Austin-2
I just tried this question on IRC but no one is about at the
moment.... I am wondering if someone can explain what is happening
wrt "[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>

_______________________________________________
Opensim-dev mailing list
[hidden email]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GetRegionByPosition - possible unnecessary work for adjacent region checks after hypergrid jump?

AJLDuarte
Hi
        I did tried to answer in IRC, guess you missed it
        The locations <x,0> are HG linked regions, ie other grid regions
placed our map on a virtual position.
        It keeps getting new numbers even when we whould expect reuse
(considering this is per region)
        Sure something isn't right on HG, so the need for the spam :(
Ubit
       
-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Ai Austin
Sent: Thursday, December 10, 2015 10:18
To: [hidden email]
Subject: [Opensim-dev] GetRegionByPosition - possible unnecessary work for
adjacent region checks after hypergrid jump?

I just tried this question on IRC but no one is about at the moment.... I am
wondering if someone can explain what is happening wrt "[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>

_______________________________________________
Opensim-dev mailing list
[hidden email]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev

_______________________________________________
Opensim-dev mailing list
[hidden email]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: GetRegionByPosition - possible unnecessary work for adjacent region checks after hypergrid jump?

Ai Austin-2
In reply to this post by Ai Austin-2
Unit wrote:
>Hi
>         I did tried to answer in IRC, guess you missed it
>         The locations <x,0> are HG linked regions, ie other grid regions
>placed our map on a virtual position.
>         It keeps getting new numbers even when we whould expect reuse
>(considering this is per region)
>         Sure something isn't right on HG, so the need for the spam :(


Many thanks.. I posted a mantis issue on this then, along with your comment

http://opensimulator.org/mantis/view.php?id=7781 

_______________________________________________
Opensim-dev mailing list
[hidden email]
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
Loading...