Jump to content

Revived JIRA for increase in memory limit


Arduenn Schwartzman
 Share

You are about to reply to a thread that has been inactive for 1886 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

4 hours ago, Love Zhaoying said:

It’s fun reading this post. Because people like talking about stuff they don’t know, which is easily disproven with wiki articles and google searches.

Easily disproved with a few minutes logged in .. no need to dirty your hands with wiki pages or (heaven forbid) publicly available source code.

Link to comment
Share on other sites

10 minutes ago, CoffeeDujour said:

The onus is on you to back up your claims with credible sources ...  as to the best of our knowledge, they have never said any of that either verbally or in published documentation or even in the published source code. 

Remember 

UWIHykS.jpg

Source for what and who are you refering too? There are several pages in the SL wiki alone.

Link to comment
Share on other sites

5 minutes ago, steph Arnott said:

Good,, you can actually read that on the wiki. Also FYI more and more over the years script processing of data is client side. Tells you that as well.

Please find and post a link to the section of the wiki that states scripts use more memory for clients running on Windows vs Linux or that scripts do anything at all clientside.

 

  • Like 1
Link to comment
Share on other sites

On 2/19/2019 at 12:24 AM, steph Arnott said:

Also Mono uses the most memory when user are using Windows. Test showed that Linux users use less. This is due to the fact that scripts are also on the clients end.

Steph, if you're referring to the section of the wiki article on Mono "mono memory myths" http://wiki.secondlife.com/wiki/Mono#Mono_Memory_Myths  I think that if you re-read it, you'll see he's talking about what happened when he tried running Mono in OpenSim on his computer in Windows vs Linux environments   That is, he downloaded the OpenSim virtual world "Nu Athens" and ran it on his pc in both Windows and Linux environments to see how memory use differed (the wiki suggests that this isn't a valid test but that's not my point).

If you're hosting an OpenSim virtual world on your PC, then of course all the script processing happens there on the host PC.   But that's not what happens with SL, where scripts are run on simulators hosted on LL's computers in the US.     

The only things that get processed client-side with SL, as far as I know, are instructions to your CPU and GPU to play visual effects like animations, particles and llTargetOmega in non-physical objects,  and to play sounds.    The scripts that trigger the animations and sounds and particles and so on are all held on LL's servers and that's where they run.

Edited by Innula Zenovka
  • Like 1
Link to comment
Share on other sites

22 minutes ago, CoffeeDujour said:

It is also worth pointing out that OpenSim is entirely distinct and separate from the 100% secret sauce server code LL use.

Second Life and OpenSim are very different beasts.

But, to be fair, Mono itself is not LL's code. It's an open-source, multi-platform programming language. (link, link)

Probably not related at all, but it's a fun fact.

Edited by Wulfie Reanimator
  • Like 2
Link to comment
Share on other sites

4 hours ago, Gabriele Graves said:

I think you mean "moot" and clearly you didn't read Qie's response from Simon Linden here:

https://community.secondlife.com/forums/topic/433004-revived-jira-for-increase-in-memory-limit/?do=findComment&comment=1857315

I have read enough about the subject outputed by LL. It is clearly stated as to why the 64k limit was set and that it was not what was planned. It was set to that to stop a minority of LSL2 scripts from breaking. Mono was not implemented for the clients benefit, it was implimented for LLs benefit. Also Mr Miguel de Icaza wrote an article about the implimentation of Mono for SL years ago. Ergo LL are not going to increase the limit set and i do not blame them because it has been proven over the years that the more coders get the worse their code gets creating over bloated programs full of garbage. There is no valid reason to increase the limit above 64k, also LL allow clients to use there own servers to communicate with the SL servers. It would vastly improve scripts if many stopped using 512kb for user coded functions which do nothing of value. Or writing twenty odd if statements without stacking them into relevent blocks and sub blocks. Or for that matter understanding the difference and usage between 'if' and 'else if'. Even something as simple as declaring the correct type instead of using integers where floats, using channel filters, removing all comments in the usage script etc etc.

Some time late last year LL changed something or things because scripts now have to be more explicit.

Link to comment
Share on other sites

1 hour ago, steph Arnott said:

I have read enough about the subject outputed by LL. It is clearly stated as to why the 64k limit was set and that it was not what was planned. It was set to that to stop a minority of LSL2 scripts from breaking. Mono was not implemented for the clients benefit, it was implimented for LLs benefit. Also Mr Miguel de Icaza wrote an article about the implimentation of Mono for SL years ago. Ergo LL are not going to increase the limit set and i do not blame them because it has been proven over the years that the more coders get the worse their code gets creating over bloated programs full of garbage. There is no valid reason to increase the limit above 64k, also LL allow clients to use there own servers to communicate with the SL servers. It would vastly improve scripts if many stopped using 512kb for user coded functions which do nothing of value. Or writing twenty odd if statements without stacking them into relevent blocks and sub blocks. Or for that matter understanding the difference and usage between 'if' and 'else if'. Even something as simple as declaring the correct type instead of using integers where floats, using channel filters, removing all comments in the usage script etc etc.

Some time late last year LL changed something or things because scripts now have to be more explicit.

But..but..

1) Mono implementation memory use has absolutely zero to do with how LSL2 works. They are different implementations, period.

2) Mono language implementation (syntax) did not change last year.

Link to comment
Share on other sites

1 minute ago, Love Zhaoying said:

But..but..

1) Mono implementation memory use has absolutely zero to do with how LSL2 works. They are different implementations, period.

2) Mono language implementation (syntax) did not change last year.

1) 64kb was not the intended limit, 32kb was. It is written in black and white on the wiki.

2) Yes it has, and many have noticed it.

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 1886 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...