I've now tested using the dpkg patch disabling fsync(), and ran each test three times, first comparing the normal dpkg with the Dir::Bin::dpkg wrapper, and next comparing the patched dpkg with the patched dpkg and the Dir::Bin::dpkg wrapper:
Sun Sep 21 09:21:28 CEST 2014 used: 750 default Sun Sep 21 09:30:53 CEST 2014 used: 562 dpkg_conf Sun Sep 21 09:43:32 CEST 2014 used: 756 default Sun Sep 21 09:53:02 CEST 2014 used: 567 dpkg_conf Sun Sep 21 10:06:25 CEST 2014 used: 800 default Sun Sep 21 10:15:47 CEST 2014 used: 559 dpkg_conf The 'default' average is 769+-32 seconds, the 'dpkg_conf' average is 563+-5 seconds. Sun Sep 21 10:33:15 CEST 2014 used: 772 dpkg_nofsync Sun Sep 21 10:42:38 CEST 2014 used: 560 dpkg_conf Sun Sep 21 10:55:19 CEST 2014 used: 758 dpkg_nofsync Sun Sep 21 11:04:43 CEST 2014 used: 561 dpkg_conf Sun Sep 21 11:17:23 CEST 2014 used: 757 dpkg_nofsync Sun Sep 21 11:26:45 CEST 2014 used: 559 dpkg_conf The 'dpkg_nofsync' average is 762+-10 seconds, the 'dpkg_conf' average is 560+-1 seconds. So the advantage of disabling fsync() in dpkg itself seem neglectable, while the advantage of using eatmydata is significant, also with a patched dpkg. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
