Re: [opensource-dev] 2.0 Absolute Dealbreaker - script count feature request

2010-10-02 Thread Kelly Linden
On Sat, Oct 2, 2010 at 4:40 PM, Argent Stonecutter wrote: > On 2010-09-29, at 18:06, Kelly Linden wrote: > > * In the end the number of scripts shouldn't be important. I have lofty > desires to remove the arbitrary limit on script size so that we can stop the > silly games of splitting scripts apa

Re: [opensource-dev] 2.0 Absolute Dealbreaker - script count feature request

2010-10-02 Thread Argent Stonecutter
On 2010-09-29, at 18:06, Kelly Linden wrote: > * In the end the number of scripts shouldn't be important. I have lofty > desires to remove the arbitrary limit on script size so that we can stop the > silly games of splitting scripts apart because you need 10k more memory than > the default. On t

Re: [opensource-dev] TCMalloc Memory Profiling?

2010-10-02 Thread Boroondas Gupte
On 10/02/2010 09:57 PM, miss c wrote: > I saw the memoryprofiling debug option to enable the TCMalloc's memory > profiling. Reading up on it here > http://goog-perftools.sourceforge.net/doc/tcmalloc.html I guess you're talking about the "MemProfiling" debug setting? (When talking about less well

Re: [opensource-dev] 2.0 Absolute Dealbreaker - script count feature request

2010-10-02 Thread Robert "Exile In Paradise" Murphey
On Sat, 2010-10-02 at 10:43 +0200, Zi Ree wrote: > Unless we get *proper* metrics on cpu time and memory consumption, all this > talk about script conut and memory is utterly useless and will only confuse > people and lead to drama. One approach is to use a cost-per-LSLcall function to generate

[opensource-dev] TCMalloc Memory Profiling?

2010-10-02 Thread miss c
I saw the memoryprofiling debug option to enable the TCMalloc's memory profiling. Reading up on it here http://goog-perftools.sourceforge.net/doc/tcmalloc.html Will this enhance the performance of my viewer or is this legacy? If it will enhance it, why is this option not on by default? Can s

Re: [opensource-dev] 2.0 Absolute Dealbreaker - script count feature request

2010-10-02 Thread Robert Martin
On Sat, Oct 2, 2010 at 12:34 PM, miss c wrote: > THANK YOU, what he said.  Why lie and make up some weird inaccurate number > to leave people guessing, just give us a script counter, LOL. > what i would suggest is 1 have a way to see TOTAL scripts LSL scripts and Mono scripts 2 if any ARC type num

[opensource-dev] Platform specific static quick download links to latest installers

2010-10-02 Thread CG Linden
Shortened quick links: http://bit.ly/viewer-dev-latest-Linux http://bit.ly/viewer-dev-latest-Mac http://bit.ly/viewer-dev-latest-Windows All results: http://bit.ly/viewer-dev-latest On Thu, Sep 23, 2010 at 2:59 PM, CG Linden wrote: > The links are now active. > -- > cg > > > On Thu, Sep 23, 2

Re: [opensource-dev] 2.0 Absolute Dealbreaker - script count feature request

2010-10-02 Thread miss c
THANK YOU, what he said. Why lie and make up some weird inaccurate number to leave people guessing, just give us a script counter, LOL. From: Erik Anderson To: Bryon Ruxton Cc: opensource-dev@lists.secondlife.com Sent: Fri, October 1, 2010 9:05:41 PM Subject

Re: [opensource-dev] 2.0 Absolute Dealbreaker - script count feature request

2010-10-02 Thread Lance Corrimal
Am Samstag 02 Oktober 2010 schrieb Ponzu: > On Sat, Oct 2, 2010 at 4:43 AM, Zi Ree wrote: > > Am Samstag 02 Oktober 2010 03:19:13 schrieb Bryon Ruxton: > > > > Unless we get *proper* metrics on cpu time and memory > > consumption, all this talk about script conut and memory is > > utterly useless

Re: [opensource-dev] 2.0 Absolute Dealbreaker - script count feature request

2010-10-02 Thread Ponzu
On Sat, Oct 2, 2010 at 4:43 AM, Zi Ree wrote: > Am Samstag 02 Oktober 2010 03:19:13 schrieb Bryon Ruxton: > > Unless we get *proper* metrics on cpu time and memory consumption, all this > talk about script conut and memory is utterly useless and will only confuse > people and lead to drama. > > T

Re: [opensource-dev] 2.0 Absolute Dealbreaker - script count feature request

2010-10-02 Thread Zi Ree
Am Samstag 02 Oktober 2010 03:19:13 schrieb Bryon Ruxton: > Q, in this case, I disagree. Changing the SCRIPT_MEMORY reports later will > not technically break content, it would just requires to slightly alter the > interpretation of it. Modifying the cap variables for event(s) to lower You never