summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20120312/006716.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-discuss/20120312/006716.html')
-rw-r--r--zarb-ml/mageia-discuss/20120312/006716.html126
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120312/006716.html b/zarb-ml/mageia-discuss/20120312/006716.html
new file mode 100644
index 000000000..42a1d8afb
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20120312/006716.html
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-discuss] How to prune urpmi-proxy cache?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20How%20to%20prune%20urpmi-proxy%20cache%3F&In-Reply-To=%3C201203122105.22087.alien%40rmail.be%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="006708.html">
+ <LINK REL="Next" HREF="006702.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] How to prune urpmi-proxy cache?</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20How%20to%20prune%20urpmi-proxy%20cache%3F&In-Reply-To=%3C201203122105.22087.alien%40rmail.be%3E"
+ TITLE="[Mageia-discuss] How to prune urpmi-proxy cache?">alien at rmail.be
+ </A><BR>
+ <I>Mon Mar 12 21:05:22 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="006708.html">[Mageia-discuss] How to prune urpmi-proxy cache?
+</A></li>
+ <LI>Next message: <A HREF="006702.html">[Mageia-discuss] Vote for board
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6716">[ date ]</a>
+ <a href="thread.html#6716">[ thread ]</a>
+ <a href="subject.html#6716">[ subject ]</a>
+ <a href="author.html#6716">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op maandag 12 maart 2012 10:59:37 schreef Morgan Leijstr&#246;m:
+&gt;<i> m&#229;ndagen den 12 mars 2012 07.49.42 skrev Maarten Vanraes:
+</I>[...]
+&gt;<i> &gt; I've been thinking along these lines:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; 1) delete older versions of the same file in the same directories
+</I>&gt;<i>
+</I>&gt;<i> That is the best.
+</I>&gt;<i>
+</I>&gt;<i> ( I wonder if it shold be possible to keep old versions, but if any client
+</I>&gt;<i> needs it it will simply be downloaded again, and i guess it will not happen
+</I>&gt;<i> very often. skip list seems overkill. )
+</I>&gt;<i>
+</I>&gt;<i> &gt; 2) give a configurable max size and delete the older files if the size is
+</I>&gt;<i> &gt; reached
+</I>&gt;<i>
+</I>&gt;<i> Yes. Size per folder or whole urpmi-proxy, or both?
+</I>&gt;<i>
+</I>&gt;<i> &gt; 3) give a configurable time limit and delete all files older than this
+</I>&gt;<i> &gt; one (in a cronjob)
+</I>&gt;<i>
+</I>&gt;<i> That should be able to be set by folder, i.e i want to give mga1 2 years,
+</I>&gt;<i> (to facilitate new installs or reinstalls) but cauldron only a couple
+</I>&gt;<i> months.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> How would theese be combined?
+</I>&gt;<i>
+</I>&gt;<i> Idea to alow any content until max size is reached, and then prioritise:
+</I>&gt;<i>
+</I>&gt;<i> If size of folder is too large, then
+</I>&gt;<i> remove old versions until size is under limit
+</I>&gt;<i> if no more old versions, then
+</I>&gt;<i> remove eldest files until size is under limit
+</I>&gt;<i>
+</I>&gt;<i> Easiets to apply per folder only
+</I>&gt;<i>
+</I>&gt;<i> Will be complicated to apply globally
+</I>&gt;<i> Maybe by &quot;outer control loop&quot; that adjust down max size per folder if total
+</I>&gt;<i> limit is reached. )
+</I>&gt;<i>
+</I>&gt;<i> So if the OP suddenly realise he need more space for other thinks he can
+</I>&gt;<i> just adjust down urpmi-proxy max size and trigger the cleaning, and all he
+</I>&gt;<i> will get space easily, prioritising is taken care of.
+</I>&gt;<i>
+</I>&gt;<i> ... i will stop fantasising now...
+</I>[...]
+
+I was rather thinking to have the old files removed on-demand...
+
+ie: if you're requesting foo-2.3.4-5.mga2, i can safely remove foo-2.3.4.4mga2
+in the same path. (if at all possible, maybe i would also try to remove
+packages which are obsoleted by this package; but i donno if that's easily and
+efficiently doable, though )
+
+thus keeping everything nice and tidy.
+
+
+about the other two parts, i didn't think about limiting it per folder or
+something, it seems like quite some configuration to be done, and rather
+complex...
+
+i'll think about that later...
+
+however, you did give me the idea that maybe it would be interesting to clean
+older files in folders which have the highest request rates or maybe the most
+recent request rates...
+
+this would clean up older files which are not often requested in folders which
+seem to update frequently, thus in folders which have the lowest cache-hit-
+rates
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="006708.html">[Mageia-discuss] How to prune urpmi-proxy cache?
+</A></li>
+ <LI>Next message: <A HREF="006702.html">[Mageia-discuss] Vote for board
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6716">[ date ]</a>
+ <a href="thread.html#6716">[ thread ]</a>
+ <a href="subject.html#6716">[ subject ]</a>
+ <a href="author.html#6716">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
+mailing list</a><br>
+</body></html>