Region

Template:Needs Translation/de Template:Needs Translation/es Template:Needs Translation/el Template:Needs Translation/he Template:Needs Translation/ko Template:Needs Translation/nl Template:Needs Translation/hu Template:Needs Translation/no Template:Needs Translation/da Template:Needs Translation/sv Template:Needs Translation/tr Template:Needs Translation/pl Template:Needs Translation/pt Template:Needs Translation/ru Template:Needs Translation/th Template:Needs Translation/uk Template:Needs Translation/zh-Hans Template:Needs Translation/zh-Hant

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).

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<sup class="TablePager_nav" style="font-size:75%;" id="fn_1" title="SL Knowledge Base: Information about Openspaces (Void Regions)">[1]. On the other hand void regions are hosted 4 per cpu but 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].

To learn more about the servers hosting SL, you can read the series of articles that have been posted to the SL blog.

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.

Footnotes

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