incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-654) Share cache with locking
Date Fri, 30 Nov 2007 23:08:43 GMT

    [ https://issues.apache.org/jira/browse/IVY-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547330
] 

Xavier Hanin commented on IVY-654:
----------------------------------

I've started working on this issue, trying to implement cache locking to be able to share
a cache among multiple concurrent resolves. The idea is to use locking only for the repository
cache, the resolution cache (which can now be split thanks to IVY-628 basic implementation)
remaining a per process non sharable cache.

I've not finished my implementation, I still have to lock some more things (marked as TODO
in BasicResolver) Hopefully I will address these problems this week-end. 

As a side effect I' ve worked on the cache implementation and increased the responsiblities
of the cache manager, decreasing those of the resolver. This is a first step toward the highly
requested IVY-399.


> Share cache with locking
> ------------------------
>
>                 Key: IVY-654
>                 URL: https://issues.apache.org/jira/browse/IVY-654
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>
> Currently it isn't possible use the same cache from multiple processes. This is a problem
in some situations, especially for build servers, which have to use one cache per process,
defeating some of the purpose of the cache. Adding an option allowing to use cache locking
to ensure the repository cache can be used by concurrent build would be a nice improvement.
> To avoid degrading performance of local builds where the cache is not shared, this should
only be an option.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message