[Expired for squid3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: squid3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665292
Hi,
trying to clean up a few old bugs.
There was no further feedback for years and also no vast list of other similar
reports that might indicate a general problem affecting more use-cases.
Furthermore Xenial nowadays is only in ESM and an issue like this unlikely to
be still fixed.
Therefore I
Thanks Amos. This is very helpful. Erik, I think my requests comment 2
still stand, except that instead of doing a bisection you could just try
applying that patch to the squid version in Xenial instead to see if
that fixes it. Or if you want to try things in a different order, that's
fine. I just
FYI: If it was upstream then I suspect it is most likely this upstream change,
none of the others had much performance gain in upstream tests:
http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-14061.patch
--
You received this bug notification because you are a member of Ubuntu
Thank you for your report and helping to make Ubuntu better.
Can you build 3.5.12 from source/gz and try that for comparison, to
ensure that it is the upstream version that causes the difference,
rather than the way it is built in packaging in 16.04? And to double
check, if you build 3.5.23 in a
