[Bugs] [Bug 1439731] Sharding: Fix a performance bug
bugzilla at redhat.com
bugzilla at redhat.com
Mon May 29 09:57:55 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1439731
Divya <divya at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |divya at redhat.com
Flags| |needinfo?(kdhananj at redhat.c
| |om)
--- Doc Text *updated* ---
Previously, a bug in shard's in-memory cache invalidation in STAT fop was causing it to send lots of LOOKUPs as part of cache-invalidation, even when the file was not undergoing any modification. As a consequence, every STAT call from the application to be followed by a LOOKUP, leading to sub-optimal performance of I/O operations on the VMs. With this fix, in-memory cache invalidation in shard's STAT operation was corrected. Now, in a pure-read workload, there was not as many LOOKUPs as the number of STATs, leading to improved VM performance. This also benefited performance in mixed read-write workload from the VMs.
--- Comment #10 from Divya <divya at redhat.com> ---
Krutika,
Could you please review and sign-off the edited doc text?
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9WolngRdb9&a=cc_unsubscribe
More information about the Bugs
mailing list