e.g.) and hardware.
> Best,
> Vasily
> --
> Vasily Tarasov,
> Research Staff Member,
> Storage Systems Research,
> IBM Research - Almaden
>
> - Original message -
> From: Sven Oehme
> To: gpfsug main discussion list
> Cc: Vasily Tarasov
>
Let me add just one more item to Sven's detailed reply: HAWC is especially helpful to decrease the latencies of small synchronous I/Os that come in *bursts*. If your workload contains a sustained high rate of writes, the recovery log will get full very quickly, and HAWC won't help much (or can
Hi Ken,
what the documents is saying (or try to) is that the behavior of data in
inode or metadata operations are not changed if HAWC is enabled, means if
the data fits into the inode it will be placed there directly instead of
writing the data i/o into a data recovery log record (which is what
Thank you Vasily and Simon for the clarification!
I was looking further into it, and I got stuck with more questions :)
- In
https://www.ibm.com/support/knowledgecenter/STXKQY_5.0.0/com.ibm.spectrum.scale.v5r00.doc/bl1adv_hawc_tuning.htm
I read:
HAWC does not change the following
That is correct. The blocks of each recovery log are striped across the devices in the system.log pool (if it is defined). As a result, even when all clients have a local device in the system.log pool, many writes to the recovery log will go to remote devices. For a client that lacks a local
