[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Caching large executable on worker nodes
- Date: Wed, 12 Aug 2015 22:00:32 +0200
- From: Jens Schmaler <jens.schmaler@xxxxxx>
- Subject: Re: [HTCondor-users] Caching large executable on worker nodes
Thanks Michael! I stumbled over these talks as well after Don mentioned
the use of SQUID. It looks as if Condor has decided to go for the SQUID
solution from 8.4.0 on, right? But what is then the future of the other
concepts? Are they just feasibility studies? Or were they competitor
ideas that ultimately did not make it?
Maybe someone of the experts could comment on this - it might be
interesting for many people working on this kind of problem.
Thanks in advance,
Am 12.08.15 um 19:18 schrieb Michael V Pelletier:
> At HTCondor Week this year there were three different presentations
> about input transfer caching including Carl's presentation regarding Squid.
> The first was "Efficently Sharing Common Data" by Zach Miller of CHTC,
> and the second was "Data Caching with HTCondor: The HTCondor CacheD" by
> Derek Weitzel with Brian Bockelman at the University of Nebraska -
> Lincoln, with Carl's rounding out the list.
> I liked the CacheD approach because the CacheD is designed as just
> another part of the HTCondor ecosystem, meaning you can do things like
> schedule or evict it, set requirements, etc. In addition, he has worked
> on using a torrent-based transfer, where an exec node can, for example,
> fetch its inputs from one or more other peers which are already running
> the job.
> The Wednesday presentations on "Data Management" started after lunch:
> Unfortunately my PowerPoint 2010 won't open Zach's presentation.
> -Michael Pelletier.
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: