Flipping through the slides from the recent SSUG meeting I noticed that
in 5.0.2 one of the features mentioned was the nsdCksumTraditional flag.
Reading up on it it seems as though it comes with a warning about
significant I/O performance degradation and increase in CPU usage. I
also recall that data integrity checking is performed by default with
GNR. How can it be that the I/O performance degradation warning only
seems to accompany the nsdCksumTraditional setting and not GNR? As
someone who knows exactly 0 of the implementation details, I'm just
naively assuming that the checksum are being generated (in the same
way?) in both cases and transferred to the NSD server. Why is there such
a penalty for "traditional" environments?
-Aaron
--
Aaron Knister
NASA Center for Climate Simulation (Code 606.2)
Goddard Space Flight Center
(301) 286-2776
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
