You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2011/09/12 14:43:08 UTC

[jira] [Created] (LOG4NET-312) Review whether ReusableStringWriter helps more than it harms

Review whether ReusableStringWriter helps more than it harms
------------------------------------------------------------

                 Key: LOG4NET-312
                 URL: https://issues.apache.org/jira/browse/LOG4NET-312
             Project: Log4net
          Issue Type: Task
    Affects Versions: 1.2.11
            Reporter: Stefan Bodewig
             Fix For: 1.2 Maintenance Release


While fixing LOG4NET-76 I (like the original reporter) wondered whether properly locking the ReusableStringWriter instances used in PatternConverter and AppenderSkeleton really provides any benefit over just creating fresh StringWriter instances rather than reusing existing ones.

I came up with the idea that it may be better in memory pressured environments like phones thus I shied away from simply stop using ReusableStringWriter but that reason may simply be wrong (I don't have any real experience with compact framework and friends).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

RE: [jira] [Updated] (LOG4NET-312) Review whether ReusableStringWriter helps more than it harms

Posted by Frank Watkins <FW...@RALS.com>.
Please remove me from the mailing list.

Thanks,
 
Frank 
 
Product Verification Test
Medical Automation Systems
E-mail: fwatkins@rals.com
Business Phone #: 434-951-2926
Internal Phone: x3043
 
-----Original Message-----
From: Stefan Bodewig (JIRA) [mailto:jira@apache.org] 
Sent: Monday, September 12, 2011 8:45 AM
To: log4net-dev@logging.apache.org
Subject: [jira] [Updated] (LOG4NET-312) Review whether ReusableStringWriter helps more than it harms


     [ https://issues.apache.org/jira/browse/LOG4NET-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig updated LOG4NET-312:
-----------------------------------

    Description: 
While fixing LOG4NET-212 I (like the original reporter) wondered whether properly locking the ReusableStringWriter instances used in PatternConverter and AppenderSkeleton really provides any benefit over just creating fresh StringWriter instances rather than reusing existing ones.

I came up with the idea that it may be better in memory pressured environments like phones thus I shied away from simply stop using ReusableStringWriter but that reason may simply be wrong (I don't have any real experience with compact framework and friends).

  was:
While fixing LOG4NET-76 I (like the original reporter) wondered whether properly locking the ReusableStringWriter instances used in PatternConverter and AppenderSkeleton really provides any benefit over just creating fresh StringWriter instances rather than reusing existing ones.

I came up with the idea that it may be better in memory pressured environments like phones thus I shied away from simply stop using ReusableStringWriter but that reason may simply be wrong (I don't have any real experience with compact framework and friends).


> Review whether ReusableStringWriter helps more than it harms
> ------------------------------------------------------------
>
>                 Key: LOG4NET-312
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-312
>             Project: Log4net
>          Issue Type: Task
>    Affects Versions: 1.2.11
>            Reporter: Stefan Bodewig
>             Fix For: 1.2 Maintenance Release
>
>
> While fixing LOG4NET-212 I (like the original reporter) wondered whether properly locking the ReusableStringWriter instances used in PatternConverter and AppenderSkeleton really provides any benefit over just creating fresh StringWriter instances rather than reusing existing ones.
> I came up with the idea that it may be better in memory pressured environments like phones thus I shied away from simply stop using ReusableStringWriter but that reason may simply be wrong (I don't have any real experience with compact framework and friends).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (LOG4NET-312) Review whether ReusableStringWriter helps more than it harms

Posted by "Stefan Bodewig (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LOG4NET-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig updated LOG4NET-312:
-----------------------------------

    Description: 
While fixing LOG4NET-212 I (like the original reporter) wondered whether properly locking the ReusableStringWriter instances used in PatternConverter and AppenderSkeleton really provides any benefit over just creating fresh StringWriter instances rather than reusing existing ones.

I came up with the idea that it may be better in memory pressured environments like phones thus I shied away from simply stop using ReusableStringWriter but that reason may simply be wrong (I don't have any real experience with compact framework and friends).

  was:
While fixing LOG4NET-76 I (like the original reporter) wondered whether properly locking the ReusableStringWriter instances used in PatternConverter and AppenderSkeleton really provides any benefit over just creating fresh StringWriter instances rather than reusing existing ones.

I came up with the idea that it may be better in memory pressured environments like phones thus I shied away from simply stop using ReusableStringWriter but that reason may simply be wrong (I don't have any real experience with compact framework and friends).


> Review whether ReusableStringWriter helps more than it harms
> ------------------------------------------------------------
>
>                 Key: LOG4NET-312
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-312
>             Project: Log4net
>          Issue Type: Task
>    Affects Versions: 1.2.11
>            Reporter: Stefan Bodewig
>             Fix For: 1.2 Maintenance Release
>
>
> While fixing LOG4NET-212 I (like the original reporter) wondered whether properly locking the ReusableStringWriter instances used in PatternConverter and AppenderSkeleton really provides any benefit over just creating fresh StringWriter instances rather than reusing existing ones.
> I came up with the idea that it may be better in memory pressured environments like phones thus I shied away from simply stop using ReusableStringWriter but that reason may simply be wrong (I don't have any real experience with compact framework and friends).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira