logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4NET-312) Review whether ReusableStringWriter helps more than it harms
Date Mon, 12 Sep 2011 12:45:09 GMT

     [ 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

        

Mime
View raw message