[Apt-proxy-users] first impressions of apt-proxy-v2

[Craig F. <cr...@wi...>]

I installed apt-proxy-v2 and started it up with a simple 'apt-proxy-v2&'.  
Here are my first impressions (and a few questions).

1)  Overall performance seems really good.  It is much faster than v1.

2)  After an 'apt-get update' apt-proxy-v2 eats up all spare CPU cycles for a 
good while (on my K6-233 test box) after the download is completed.  Memory 
usage also increases during this time.  What is it doing?

3)  apt-proxy-v2 seems to cache both Package/Release files  and packages just 
fine, but it never serves up the cached files!  Instead it downloads them 
from the backend with every request.  The debugging messages say:

[debug:9]CHECKING_CACHED
[debug:9]NOT_CACHED

even when the file has been cached.  This is great for building a partial 
mirror, but kinda defeats the purpose of a proxy, eh? ;-)

4)  Over time, apt-proxy-v2 continues to grow in memory with each successive 
download.  I've generally killed the process when it reached around 40MB in 
memory.

5)  What is the proper way to start apt-proxy-v2?  I've just been doing 
a 'apt-proxy-v2&' from the command prompt for testing.  Do I need any 
parameters?  Is it designed to run under inetd or as a standalone server?

6)  Is it safe to use the same cache directory for v1 and v2?  It sure would 
be nice not to have 2 separate partial mirrors being built while I test this 
thing out!

Overall, that's not bad for an alpha package!  I'll be following its progress 
closely.  Let me know how many of these issues are matters of my usage and 
configuration.


-- 
Craig Foster
cr...@wi...