And one more try at speeding up fsync-on-close by adding more threads that can
block:
```
eio_set_min_parallel(512);
eio_set_max_idle(512);
```
With 512 (the default is 4) backend threads that can block, the kernel install
time is
```
$ sudo /usr/bin/time ./rpm -U --root=/var/tmp/xxx --nodeps --force
kernel-3.10.0-514.26.2.el7.x86_64.rpm
...
5.77user 1.10system 0:17.79elapsed 38%CPU (0avgtext+0avgdata 37968maxresident)k
0inputs+300120outputs (0major+21579minor)pagefuls 0swaps
```
And both fdatasync+fsync are being run (by inspection).
So the reasoning in the previous comment (~2.5x slower for fsync-on-close,
quite acceptable, etc) seems correct correct even if I had a brain fart while
tinkering ;-)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/258#issuecomment-320499489
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
