public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Merge Window Closing Announcement for Core Update 127
Date: Sun, 13 Jan 2019 12:14:19 +0000	[thread overview]
Message-ID: <14489638-338E-49C8-994D-5678496FB6F6@ipfire.org> (raw)
In-Reply-To: <5d24f84f-e12d-cb00-0847-b2077e84165a@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]

Hi,

> On 13 Jan 2019, at 10:04, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> On 10.01.2019 15:22, Michael Tremer wrote:
>> Hello guys,
> 
> Hi,
> 
>> Upon request, I would like to announce that on Saturday, 12th Jan, we are going to branch Core Update 127.
>> 
>> This means that we no longer accept any patches that introduce any new features and only accept patches that fix any bugs introduced. Nothing new here, you all know how this works :)
>> 
>> This announcement is just coming now so that you all know this. It is a bit short notice this time, but I hope I will be better with this next time round. In the past some patches have been submitted after the merge window closed and had to be deferred to the next Core Update to the frustration of the submitters. Therefore, we now try this and hope that we can make the process better for everyone who is contributing!
>> 
>> We have an update with many new features here. Please help testing as soon as the first build is available.
>> ...
> 
> Thanks for the reminder, but regarding this Core update, one question is
> bothering me:
> 
> Did anyone had the chance to test 'squid 4.5' - especially along with
> this commit
> (https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=eedca6e36c1131ce5542da5ccbfbb5667648c024
> => "squid: Run as many redirectors as we have CPU cores") - in a
> productive environment?
> 
> During my first tests, I got occasional warnings like "idnsSendQuery FD
> 8: sendto: (1) Operation not permitted" or "WARNING: All 2/2 redirector
> processes are busy" in squid 'cache.log' and I'd like to clarify
> possible mistakes in advance.
> 
> By now, I'm running the untuned parameters from current 'next' and these
> errors haven't appeared for some time now. Furthermore, 'testing tree'
> exists, ( ;-) ) but did anyone had a chance to try this?

I sent squid thousands of requests with ab (Apache Benchmark) and that worked fine with only one redirector.

Best,
-Michael

> 
> Best,
> Matthias


  reply	other threads:[~2019-01-13 12:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 14:22 Michael Tremer
2019-01-10 18:19 ` Peter Müller
2019-01-13 10:04 ` Matthias Fischer
2019-01-13 12:14   ` Michael Tremer [this message]
2019-01-13 12:43     ` Matthias Fischer
2019-01-13 14:24       ` Aw: " Bernhard Bitsch
2019-01-14 10:43         ` Michael Tremer
2019-01-14 13:32           ` Bernhard Bitsch
2019-01-14 15:28             ` Michael Tremer

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=14489638-338E-49C8-994D-5678496FB6F6@ipfire.org \
    --to=michael.tremer@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