[Opensim-dev] The Future of Open Simulator(?) (UNCLASSIFIED)

Justin Clark-Casey jjustincc at googlemail.com
Tue Aug 18 10:50:51 UTC 2015


On point 2, the coding standards are pretty much the C# guidelines at [1]
(I thought there used to be a longer doc but can't find it on a quick
google).

On point 3, this is very true.  It's a problem of the codebase having grown
organically with many different developers of varying skill levels.

During the 2013 and 2014 OSCC conferences I spent a lot of time on
scalability but much of this was ad-hoc fixes or measurement tooling.  The
advantage of being extremely thread happy is that if one thread gets
blocked (e.g. waiting on I/O) then this won't halt other threads (assuming
it isn't in a locked region).  But the disadvantage is unpredictable
performance and overhead though I don't know how much.

I believe any VW engine eventually need something like an OS scheduler to
control work performance and make sure that CPU utilization is efficient
and handles degradation gracefully at 100% utilization.  However, that's an
extremely tough problem and I'm not sure it's even possible in a managed
language.

On point 4, I believe any future is gradual evolution.  The investment
required for radical change is simply too high.  Perhaps it would be easier
if some way can be found to break apart monolithic VW systems but then
monoliths have continued to win in the operating system space (Linux vs
micro-kernels for instance) and I think operating systems have many
similarities with user script executing virtual worlds.

-- Justin

-- Justin

[1] https://msdn.microsoft.com/en-us/library/ff926074.aspx

On Thu, Aug 13, 2015 at 5:32 PM, Cinder Roxley <cinder at alchemyviewer.org>
wrote:

> On August 13, 2015 at 8:14:30 AM, Maxwell, Douglas CIV USARMY ARL (US) (
> douglas.maxwell3.civ at mail.mil) wrote:
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Can someone explain to me why the core developers insist on control of the
>
> code, but refuse to manage the project? I ask again: what are your plans
> for
> the future of Open Simulator? It's ok to say you don't have any, let's make
>
> some!
>
> I'll throw out some ideas based on the MOSES goals and objectives:
>
> 1) Scale limitations lifted. We need a system that is governed by its
> available hardware and network resources, not bound by software limits.
>
> 2) Let's create clear definitions of "stability".
>
> 3) Clear and up-to-date API documentation.
>
> 4) Clear and up-to-date OS deployment guidance under numerous typical
> network
> topologies.
>
> 5) Bug identification & reduction.
>
> 6) Efficient ray tracing. Useful for simulation of sensors as well as
> naturalized bot interactions.
>
> 7) N-body physics. Would be nice to have vehicles that can follow terrain
> and not look like Star Wars land speeders. Would also be nice to have more
>
> natural avatar movement rather than the rigid animations we use now.
>
> What are yours? Anyone?
>
> v/r -doug
>
> This can be considered my “wish list” as I don’t really have a say in what
> happens, but I’m willing to put in a fair share of work in seeing that it
> can be done if others agree these are desirable targets:
>
> 1) Restating what Doug has mentioned, Clear and up-to-date API
> documentation. This hinders contributors, myself included, from working on
> things and leads to a lot of frustration and disappointed from
> well-intentioned folks.
>
> 2) A coding standard that defines and formalizes the style of code used
> throughout the codebase and is adhered to and enforced and should be
> pointed to often and regularly for contributions. Good code is easy to read
> and manageable. A formal coding standard is a good step in that direction.
>
> 3) OpenSim is a thread monster. There doesn’t seem to be any sort of
> approach to how threading is handled. This I think would fall under Doug’s
> criteria for #1.
>
> 4) I think it’s time to hop off the fence and decide whether to maintain
> the Second Life protocol compatibility, (Which, let’s be honest, is pretty
> lacking. There’s a lot missing post-2010.) or to break new ground. Linden
> Lab has apparently made their decision regarding that. There are viewer
> developers out there willing to work with OpenSimulator is doing this. I am
> one of them. I just can’t be in IRC all the time, but I want to do this
> with you guys and I know there are others out there willing to put in the
> work to build clients to connect to new and better worlds with sensible
> protocols.
>
> Please don’t take any of this as criticism as it is not meant as such. I
> appreciate all the work that everyone on this project and who is affiliated
> with it does.
> --
> Cinder Roxley
> Sent with Airmail
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at opensimulator.org
> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20150818/d7f8c6cb/attachment.html>


More information about the Opensim-dev mailing list