Difference between revisions of "Region"

From Second Life Wiki
Jump to navigation Jump to search
m
Line 14: Line 14:
|Glossary=*
|Glossary=*
}}
}}
Simulator or Sim(short for simulator) is in common usage, a Second Life region. "Sim" may also refer to the server host machine, for example sim1234.agni.lindenlab.com. The SL server grid consists of over 5000 servers. Each server hosts several simulator processes (regions, or "sims"), of which there are over 22,000 (as of July 2008).


A named 256m x 256m (65,536 m²) area hosted by a single simulator process.  In common usage, the term "simulator" or "sim" may also refer to a region, but in fact a single sim process can host mulitple regions.


The land in SL is hosted on dual-core dual-cpu Linux servers. Each region is 65,536 m² (256x256m), there are two types of regions: Normal and Void. A server hosting normal regions hosts two regions, one per cpu{{Footnote|1={{slkb|4235|Information about Openspaces (Void Regions)}}|2={{Slkb|4235|Information about Openspaces (Void Regions)|no-link=*}}|handle=cpu}}. On the other hand void regions are hosted 4 per cpu but support fewer prims and users{{Footnote|handle=cpu}}.
There are two types of regions: Normal and Void. There are two normal regions per server host CPU{{Footnote|1={{slkb|4235|Information about Openspaces (Void Regions)}}|2={{Slkb|4235|Information about Openspaces (Void Regions)|no-link=*}}|handle=cpu}} and four void regions per server host CPU.  Void regions support fewer prims and users{{Footnote|handle=cpu}}.


To learn more about the servers hosting SL, you can read the series of articles that have been posted to the [http://blog.secondlife.com/?s=%22class+5%22 SL blog].
For more information about server hosts, see the [http://blog.secondlife.com/?s=%22class+5%22 Second Life blog].


== Effects on Scripting ==
== Effects on Scripting ==


Scripts can detect their current region, and can detect region changes, but these factors are normally separate from region coordinates. There is a delay associated with an object moving from one region to another, this happens because object and all of it's scripts states must be serialized, sent to the new region, and deserialized.
Scripts can detect the current region, and detect region changes, but these factors are normally separate from region coordinates. There is a delay associated with an object moving from one region to another, because the object and its script's states are serialized, sent to the new region, and then deserialized.


== Footnotes ==
== Footnotes ==
{{Footnotes}}
{{Footnotes}}

Revision as of 14:58, 15 December 2008

A named 256m x 256m (65,536 m²) area hosted by a single simulator process. In common usage, the term "simulator" or "sim" may also refer to a region, but in fact a single sim process can host mulitple regions.

There are two types of regions: Normal and Void. There are two normal regions per server host CPU<sup class="TablePager_nav" style="font-size:75%;" id="fn_1" title="SL Knowledge Base: Information about Openspaces (Void Regions)">[1] and four void regions per server host CPU. Void regions support fewer prims and users<sup class="TablePager_nav" style="font-size:75%;" id="fn_1" title="SL Knowledge Base: Information about Openspaces (Void Regions)">[1].

For more information about server hosts, see the Second Life blog.

Effects on Scripting

Scripts can detect the current region, and detect region changes, but these factors are normally separate from region coordinates. There is a delay associated with an object moving from one region to another, because the object and its script's states are serialized, sent to the new region, and then deserialized.

Footnotes

  1. ^ SL Knowledge Base: Information about Openspaces (Void Regions)