On 07/01/2011 12:01 AM, Sašo Kiselkov wrote:
> On 06/30/2011 11:56 PM, Sašo Kiselkov wrote:
>> Hm, it appears I'll have to do some reboots and more extensive testing.
>> I tried tuning various settings and then returned everything back to the
>> defaults. Yet, now I can ramp the number of concurrent output streams to
>> ~170 instead of the original 95 (even then the pool still has capacity
>> left, I'm actually running out of CPU power). The txg commit occurs at
>> roughly every 15 (or so) seconds, which is what I wanted. Strange that
>> this occurs even after I returned everything to the defaults... I'll try
>> doing some more testing on this once I move the production deployment to
>> a different system and I'll have more time to experiment with this
>> machine. Anyways, thanks for the suggestions, it helped a lot.
>> Regards,
>> --
>> Saso
> Just a follow correction: one parameter was indeed changed:
> zfs_write_limit_inflated. In the source it's set to zero, I've set it to
> 0x200000000.

So it seems I was wrong after all and it didn't help. So the question
remains: is there a way how to force ZFS *NOT* to commit a txg before a
certain minimum amount of data has accumulated in it, or before the txg
timeout is reached?

All the best,
zfs-discuss mailing list

Reply via email to