> Finally, however, we have to do journal replay --- looking for the > most uptodate copies of each block in the journal and writing them > back to disk. This is again a sequential scan through the journal, > but the writebacks are NOT sequential and can cause a lot of seeking. > I suspect that that is where the bulk of the time is spent. What about sorting those writebacks before commiting them to disk? Or should the disksubsystem take care of that trough that elevator-alg.? ================================================ De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. ================================================ The information contained in this message may be confidential and is intended to be exclusively for the addressee. Should you receive this message unintentionally, please do not use the contents herein and notify the sender immediately by return e-mail.
