devZer0

yes, i could do that

it does not help for my test case. even worse - i see metadata getting evicted and arc collapsing with a metadata-only workload. on a VM (4gb ram) i created...

can somebody keep an eye on this and/or confirm/deny my observation at https://github.com/openzfs/zfs/issues/12028#issuecomment-1278594949 ? thanks!

i explicitly mean the number/count of calls, not the byte rate. that is something entirely different you can have low iops rate with high disk troughput or have high iops...

i'm not sure if we really should call that "IOPS", as IOPS is "IO Operations Per Second" and that mostly refers to disk writes/reads. and read()/write() may get pooled before...

hello, we also have massive problems with docker-compose. it does not work reliable to start containers on a host . we use docker-compose part of a ci/cd environment and jenkins...

now, months later this is still open and not further commented. is docker-composed orphaned/abandoned software nobody cares for ?

we also cannot use v2 as there is no mechanism to limit parallelism. our servers are getting totally overloaded if there are too many services getting started in parallel, i.e....

we are also using the patch in production now, with good results so far

i'm very sad that nobody cares and this is being ignored