RRD4J isn't a DB, per se, so it doesn't really have a "record" size.  In fact, 
I don't even know if, when data is written to the binary, whether it is 
contiguous or not so the amount written may not directly correlate to a proper 
record-size.

I did run your command and found the size patterns you were talking about:

              462  java    409
             3320  java    409
             6819  java    409
                5  java   1227
                1  java   1692
               16  java   3243

"409" is the number of clients I tested, so I assume it means the largest write 
it makes is "6819".  Is that bits or bytes?

Does that mean I should try setting my recordsize equal to the lowest multiple 
of 512 GREATER than 6819? (14 x 512 = 7168)
 
 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to