bug#32073: Improvements in Grep

2018-07-06 Thread Sergiu Hlihor
Hello, I'm using grep over Ubuntu Server 14.04 (Grep version 2.16). While grepping over large files I've noticed Grep is painfully slow. The bottleneck seems to be the read block which is extremely low (looks like 64KB). For large files residing over big HDD RAID arrays, this request barely re

bug#32073: Improvements in Grep

2018-07-06 Thread Paul Eggert
Sergiu Hlihor wrote: Given my tests for such scenarios, a read block size of at least 512KB would be way more efficient. Does stdio do this already? If not, why not? How could grep reasonably configure a good block size?

bug#32073: Improvements in Grep

2018-07-06 Thread Dennis Clarke
On 07/06/2018 06:06 PM, Paul Eggert wrote: Sergiu Hlihor wrote: Given my tests for such scenarios, a read block size of at least 512KB would be way more efficient. Does stdio do this already? If not, why not? How could grep reasonably configure a good block size? This seems to be a very spe

bug#32073: Improvements in Grep

2018-07-06 Thread Jim Meyering
On Fri, Jul 6, 2018 at 9:26 AM, Sergiu Hlihor wrote: > Hello, > I'm using grep over Ubuntu Server 14.04 (Grep version 2.16). While > grepping over large files I've noticed Grep is painfully slow. The > bottleneck seems to be the read block which is extremely low (looks like > 64KB). For large

bug#32073: Improvements in Grep

2018-07-06 Thread Sergiu Hlihor
To add, the increase to 128KiB is good, but for RAID arrays with light to medium load, this is not sufficient. In a system without any load, the HDD can read ahead and always serve the next request from buffer thus reading at full sequential speed of ~200MB/s . In a RAID 10 configuration with 12 hd