From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Running projects - proxy graphs rebuilt
Date: Fri, 10 Nov 2017 19:41:52 +0100 [thread overview]
Message-ID: <d52ce82e-fc7c-60d8-9ff0-b599e67f00db@ipfire.org> (raw)
In-Reply-To: <1510320180.4838.370.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Hi,
On 10.11.2017 14:23, Michael Tremer wrote:
> Hi,
>
> On Fri, 2017-11-10 at 02:42 +0100, Matthias Fischer wrote:
>> Hi,
>>
>> I have just some short question about 'sgraph' (Proxy-Diagramme):
>>
>> Should I build 'sgraphs' (Proxy-Diagramme - see:
>> https://sourceforge.net/projects/squid-graph/) as an addon for pakfire or as
>> an update for GUI integration?
>>
>> Localizations and GUI are ok - running.
>
> How much of an impact would it have when it is always installed but not
> used? Does it need to fire the cron every time?
Analyzing ~1.5 million lines took about 15-20 seconds during testing -
every five minutes - on a duo box. Because of this I moved the
'sgraph'-job temporarily from 'makegraphs' to '/etc/fcron.hourly'. But
this could lead to missing some information through rotation. Right now
its running in '/etc/fcron.cyclic', analyzing 99389 lines in under a
second every five minutes. Load is ok and no problem.
=> Impact depends on the number of machines and proxy load. As you
wrote: "Well, that is probably okay.". ;-)
> It would make sense to integrate it since the proxy is preinstalled,
> but SARG is an add-on... So probably add-on...
Addon is "under construction".
Best,
Matthias
prev parent reply other threads:[~2017-11-10 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 1:42 Matthias Fischer
2017-11-10 13:23 ` Michael Tremer
2017-11-10 18:41 ` Matthias Fischer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d52ce82e-fc7c-60d8-9ff0-b599e67f00db@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox