William Fretts-Saxton wrote: > Unfortunately, I don't know the record size of the writes. Is it as simple > as looking @ the size of a file, before and after a client request, and > noting the difference in size? This is binary data, so I don't know if that > makes a difference, but the average write size is a lot smaller than the file > size. > > Should the recordsize be in place BEFORE data is written to the file system, > or can it be changed after the fact? I might try a bunch of different > settings for trial and error. > > The I/O is actually done by RRD4J, which is a round-robin database library. > It is a Java version of 'rrdtool' which saves data into a binary format, but > also "cleans up" the data according to its age, saving less of the older data > as time goes on. >
You should tune that in application level, see https://rrd4j.dev.java.net/ down in "performance issue" section. Try the "NIO" backend and use smaller (2048?) record size... -- This space was intended to be left blank. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
