I'm moving this case to waiting needs spec as the comments
received have indicated that the scope of the environment
variables could be expanded.
Pete
___
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
+1, I have no issues.
-Seb
___
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
This case times out today but there have been no comments from
any PSARC members - any reviewers ?
thanks
pete
___
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
I have a comment: Why do you use 3 environment variables? Environment
variables are very expensive to use, they significantly increase start
up time of an application and slow down all applications which use
getenv() or putenv() if the size of the environment is large. libast
had the same problem,
IqbKmMQy1UBWIasvxNOehuw5cywibXlWkHF5ARxtYsr125Abg3ElB+Dn+QmG49OZOjJ0
nbexQuLVPvaYTcVKPQ3c4qlfhOtKFPBqwqJxc=
In-Reply-To: 4c17ba17.4060...@oracle.com
Date: Tue, 15 Jun 2010 19:58:24 +0200
Subject: Re: Performance Improvements for libmtmalloc [PSARC/2010/212
FastTrack, timeout 06/15/2010]
From: ольга
Solaris getenv() and putenv() do not scale linear and it gets a lot
*worse* above 100 or more variables. Adding 1 environment variable per
libmtmalloc tunable makes IMO no sense, it is not economic nor is it
fast to have that many variables for similar purposes.
I don't buy the comment about
On 15/06/10 03:31 PM, ольга крыжановская wrote:
Solaris getenv() and putenv() do not scale linear and it gets a lot
*worse* above 100 or more variables. Adding 1 environment variable per
libmtmalloc tunable makes IMO no sense, it is not economic nor is it
fast to have that many variables for
I already looked at the problem. This can not be fixed without
breaking binary compatibility.
Olga
2010/6/16 Darren Reed darren.r...@oracle.com:
On 15/06/10 03:31 PM, ольга крыжановская wrote:
Solaris getenv() and putenv() do not scale linear and it gets a lot
*worse* above 100 or more
Hi,
If you forward your analysis to us, we can add it to a bug for you.Surely
we can come up with a way to optimize environment handling (perhaps with a new
interface that future executables will use, while deprecating the existing
mechanism). Such pathological performance is certainly
On 06/15/10 15:31, ольга крыжановская wrote:
Solaris getenv() and putenv() do not scale linear and it gets a lot
*worse* above 100 or more variables.
Running libmicro's getenv test case indicates that this is not the case;
performance is linear with size of environment aside from cache
I am sponsoring this case for Rick Weisner.
Requested release binding: Patch
Modified man pages are in the case's materials directory and diffs
are at the end of this proposal.
Template Version: @(#)sac_nextcase 1.70 03/30/10 SMI
This information is Copyright (c) 2010, Oracle and/or its
11 matches
Mail list logo
