@ Anony--yeah, it seems like LL is very exposed to the owners of 13,000 voids/openspaces, which by definition are also the owners of the 14,000 private islands = full sims = regions. At least the renters of the 5,000 have no claim on LL!
From my discussions with various techie types there is no specific coding that would allow for a direct mapping of a region to a core. A CPU in fact does not get arithmetically more powerful as there are more cores–ie a quad core is not 2x as powerful as a dual core. So it is unlikely that a quad-core, dual cpu machine would effectively handle 8 regions under the same code that is running 2 regions on a dual-core, dual-CPU = Class 5.
In fact it would seem odd to map a Region to a core in a multiple core CPU, when in fact the usage on Regions is not flat, but more bursty depending on load. For example–why leave a core processing unit idle when there is no contention for processing. So if everyone is at a party on part of the CPU, then why reserve processing for empty “habitations”.
I am pretty sure (but actually don’t know 100%) that the Region code hits the CPU and the core is an internal CPU tool that increases parallelism of processing and pushes more work through the CPU. The whole reason that Intel started the core technology was that it could not increase CPU speed cost-effectively and parallelism was next best thing.
Also on the LL website they say that a Class 5 is a dual-core, dual-CPU and they run two regions = 1 region per CPU.
I would also doubt that even LL is dumb enough to lease a server for more than 12 months at a time. I think running 10,000 and more servers already puts them in a good enough negotiating position. I would see it more likley that they are rotating the older machines into grid services rather than hosting even voids.
@ Anony--yeah, it seems like
Tue, 11/11/2008 - 12:23 — RightAsRain Rimbaud@ Anony--yeah, it seems like LL is very exposed to the owners of 13,000 voids/openspaces, which by definition are also the owners of the 14,000 private islands = full sims = regions. At least the renters of the 5,000 have no claim on LL!
Also I just tossed a comment about core - CPU points out on a blog comment, i think this is also a very confusing point about how a Region actually runs. My comments regarding regions not running a "core" but on the "CPU":
From my discussions with various techie types there is no specific coding that would allow for a direct mapping of a region to a core. A CPU in fact does not get arithmetically more powerful as there are more cores–ie a quad core is not 2x as powerful as a dual core. So it is unlikely that a quad-core, dual cpu machine would effectively handle 8 regions under the same code that is running 2 regions on a dual-core, dual-CPU = Class 5.
In fact it would seem odd to map a Region to a core in a multiple core CPU, when in fact the usage on Regions is not flat, but more bursty depending on load. For example–why leave a core processing unit idle when there is no contention for processing. So if everyone is at a party on part of the CPU, then why reserve processing for empty “habitations”.
In fact Linden has envisioned a more dynamic virtualization for Regions, but as usual started it only and not carried it along. http://wiki.secondlife.com/wiki/AWG_Virtualization.
I am pretty sure (but actually don’t know 100%) that the Region code hits the CPU and the core is an internal CPU tool that increases parallelism of processing and pushes more work through the CPU. The whole reason that Intel started the core technology was that it could not increase CPU speed cost-effectively and parallelism was next best thing.
Also on the LL website they say that a Class 5 is a dual-core, dual-CPU and they run two regions = 1 region per CPU.
I would also doubt that even LL is dumb enough to lease a server for more than 12 months at a time. I think running 10,000 and more servers already puts them in a good enough negotiating position. I would see it more likley that they are rotating the older machines into grid services rather than hosting even voids.