On 2024-07-04 04:57, Nishant Sharma wrote:
On 03/07/24 21:27, Alex Rousskov wrote:
On 2024-07-03 09:27, Nishant Sharma wrote:
Is there any change that we need to do in the configure script to
check for the availability of 64 bit atomic lock and use 32 bit lock
if not available?
It is technic
On 03/07/24 21:27, Alex Rousskov wrote:
On 2024-07-03 09:27, Nishant Sharma wrote:
I was able to compile by replacing `uint64_t` to `uint32_t` and squid
worked with workers > 1.
Where did you replace uint64_t with uint32_t? In IdSet::Node typedef?
Any other changes? AFAICT, changing just IdSe
On 2024-07-03 09:27, Nishant Sharma wrote:
I had reported the issue to Openwrt project as well and I understood
that in order to save space, squid was being compiled for mips16 instead
of mips32.
Sorry, I do not know why/how that fact is relevant to this discussion,
but thank you for sharing
Hello,
On 28/06/24 20:01, Nishant Sharma wrote:
On 28/06/24 19:44, Alex Rousskov wrote:
I do not know the answer to your question. SMP performance penalties
are often smaller for smaller cache sizes, but cache size is not the
only performance-affecting locking-sensitive parameter, so YMMV.
I
On 28/06/24 19:44, Alex Rousskov wrote:
I do not know the answer to your question. SMP performance penalties are
often smaller for smaller cache sizes, but cache size is not the only
performance-affecting locking-sensitive parameter, so YMMV.
I was able to compile after commenting the specific
On 2024-06-28 01:38, Nishant Sharma wrote:
On 27/06/24 23:06, Alex Rousskov wrote:
and how your traffic tickles them, SMP Squid without atomic locks
might become very slow! We do not (and, IMO, should not) optimize
performance for environments without lock-free atomics!
I see the following op
Thanks for your reply Alex.
On 27/06/24 23:06, Alex Rousskov wrote:
and how your traffic tickles them, SMP Squid without atomic locks might
become very slow! We do not (and, IMO, should not) optimize performance
for environments without lock-free atomics!
I see the following options for going
On 2024-06-27 10:35, Nishant Sharma wrote:
I am running squid 6.10 on Openwrt 23.05.2, which is cross compiled for
ramips / mipsel_24kc which has a 32 bit CPU (MT7621A) with 2 cores and 2
threads.
Squid fails to start in SMP mode when I set workers > 1.
The assertion in question may be over
I have Squid 5.8 I can’t start it with multiple workers enabled in pfSense
also. It is a 64bit 2100MAX
Sent from my iPhone
> On Jun 27, 2024, at 08:12, Nishant Sharma wrote:
>
> Hello,
>
> I am running squid 6.10 on Openwrt 23.05.2, which is cross compiled for
> ramips / mipsel_24kc which ha
Has anyone ran this on a Banana Pi r3 or r4?
Sent from my iPhone
> On Jun 27, 2024, at 08:12, Nishant Sharma wrote:
>
> Hello,
>
> I am running squid 6.10 on Openwrt 23.05.2, which is cross compiled for
> ramips / mipsel_24kc which has a 32 bit CPU (MT7621A) with 2 cores and 2
> threads.
>
Hello,
I am running squid 6.10 on Openwrt 23.05.2, which is cross compiled for
ramips / mipsel_24kc which has a 32 bit CPU (MT7621A) with 2 cores and 2
threads.
Squid fails to start in SMP mode when I set workers > 1.
SMP worked fine with squid 4.13 on same architecture.
I have filed a bug
11 matches
Mail list logo
