On 01/18/2018 05:35 PM, Ivan Larionov wrote:
> * Multiple squid swap in or swap out ops reading/writing contiguous
> blocks could be merged into one 256KB IO operation.
> * Random squid operations could be handled as single 32KB IO operation.
FWIW, on a busy Squid with a large disk cache in a st
Thanks Amos.
According to AWS docs:
> I/O size is capped at 256 KiB for SSD volumes
> When small I/O operations are physically contiguous, Amazon EBS attempts
to merge them into a single I/O up to the maximum size. For example, for
SSD volumes, a single 1,024 KiB I/O operation counts as 4 operati
On 01/18/2018 04:04 PM, Ivan Larionov wrote:
> So if I understand you correctly max-swap-rate doesn't limit disk IOPS
Correct. Squid does not know what the disk- or OS-level stats are.
> but limits squid swap ops instead
If you define a "swap op" as reading or writing a single I/O page for
th
On 19/01/18 12:04, Ivan Larionov wrote:
Thank you for the fast reply!
read_ops and write_ops is AWS EBS metric and in general it correlates
with OS-level reads/s writes/s stats which iostat shows.
So if I understand you correctly max-swap-rate doesn't limit disk IOPS
but limits squid swap op
Thank you for the fast reply!
read_ops and write_ops is AWS EBS metric and in general it correlates with
OS-level reads/s writes/s stats which iostat shows.
So if I understand you correctly max-swap-rate doesn't limit disk IOPS but
limits squid swap ops instead and every squid operation could in
On 01/18/2018 03:16 PM, Ivan Larionov wrote:
> cache_dir max-swap-rate documentation says that swap in requests
> contribute to measured swap rate. However in our squid 4 load test we
> see that read_ops + write_ops significantly exceeds the max-swap-rate we
> set and squid doesn't limit it.
In t
Hello.
cache_dir max-swap-rate documentation says that swap in requests contribute
to measured swap rate. However in our squid 4 load test we see that
read_ops + write_ops significantly exceeds the max-swap-rate we set and
squid doesn't limit it.
I tried to set it to 200 to confirm that it actual
The Squid team are planning to remove the Custom XML parser used for ESI
processing from the next Squid version.
At first this seemed like a simple removal if unused functionality.
However during review of the changes it turns out this functionality may
be used in many situations when it shoul
From: Amos Jeffries
>
> Sorry I have a bit of a distraction going on ATM so have not got to that
> detailed check yet. Good to hear you found a slightly better situation >
> though.
[...]
> In normal network conditions it should rise and fall with your peak vs
