You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org> on 2011/10/05 00:40:35 UTC

[jira] [Updated] (TS-658) HTTP SM holds the cache write lock for too long

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

Leif Hedstrom updated TS-658:
-----------------------------

    Fix Version/s:     (was: 3.1.2)
                   3.2.0
    
> HTTP SM holds the cache write lock for too long
> -----------------------------------------------
>
>                 Key: TS-658
>                 URL: https://issues.apache.org/jira/browse/TS-658
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Leif Hedstrom
>             Fix For: 3.2.0
>
>
> It seems we open the cache for write very early on in the HTTP SM, which can have very bad effect on performance if the object is not cacheable. It's not totally clear as to why this is done this way, but we should examine this for v3.1, and try to minimize how long we hold the lock. It's possible this is related to read_while_writer, but then it should be modified IMO.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira