Please fill in the following information:

Issue description: Ch09 under Tuning Storage with Tuned Profiles mentions that 

• The sysfs plugin configures I/O scheduler tunables, using key=value definitions. The following example configures the fifo_batch tunable on the vda device to be 1.
  [sysfs]
  /sys/block/vda/queue/iosched/fifo_batch=1

Also next GE ch09s02 uses the same set in step 4.3 ( from 16 in step 2.3) - The learners dont have any context here as to why are we reducing it and reducing it to 1 altogether. Will setting it to 2 or 3 wont suffice ? what about CPU strain / performance - wont it have any impact bcz of this batch size as 1 ? The increased overhead of handling individual requests, frequent disk seeks, and more frequent interrupts can all contribute to higher CPU usage in this case.

Ch09s07 also uses this in step 3.3.

The optimal fifo_batch setting depends on your specific needs and workload characteristics. One must carefully consider the trade-offs and experiment to find the best configuration for your system.

ideally, course should explain:

• The specific use case or performance goal motivating the fifo_batch setting.
• The trade-offs between disabling batching (reduced latency) and enabling it (potentially higher throughput).

 FIFO scheduler when set to 1,instructs the scheduler to group only one I/O request at a time into a batch before sending it to the disk. This effectively disables batching and prioritizes each request in order of arrival - which is ideal for testing purpose on a specific workload - but is it recommended in a real production environment ?

Steps to reproduce:

Workaround:

Expected result: