> -----Original Message----- > From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> > Sent: Wednesday, July 8, 2020 11:51 AM > > On Wed, Jul 08, 2020 at 12:24:27AM -0600, Chris Murphy wrote: > > 2. Benchmarking: this is hard. A simple tool for doing comparisons > > among algorithms on a specific bit of hardware is lzbench. > > https://github.com/inikep/lzbench > > How to compile on F32. > > https://github.com/inikep/lzbench/issues/69 > > But is that adequate? How do we confirm/deny on a wide variety of > > hardware that this meets the goal? And how is this test going to > > account for parallelization, and read ahead? Do we need a lot of data > > or is it adequate to get a sample "around the edges" (e.g. slow cpu > > fast drive; fast cpu slow drive; fast cpu fast drive; slow cpu slow > > drive). What algorithm? > > More data is always better. I like qualifying the situations in that way. I > think we should make our decision based on the "center" rather than the > edges, though. > > For I hope obvious reasons, I'd love to see this tested on a Lenovo X1 > Carbon Gen 8 with the default SSD options. > I personally haven't had any experience with btrfs but if there are any guidelines on testing that we can do and what data should be collected to help out let me know and I'll see if we can hit up some of our platforms and get some numbers. Mark _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
