|To:||Ben Myers <bpm@xxxxxxx>|
|Subject:||Re: understanding speculative preallocation|
|From:||Jason Rosenberg <jbr@xxxxxxxxxxxx>|
|Date:||Fri, 26 Jul 2013 17:11:55 -0400|
|Dkim-signature:||v=1; a=rsa-sha256; c=relaxed/relaxed; d=squareup.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gd28uTxu8qihEx67uEvJ8ByR7KQU/XGFx4aIB3YyuYM=; b=OtxX8MY2Y6ggUqGaamOD5dSjnOvwduAEJUNhGShhKE//38B9KLaR6sx/WWjcSwr8PO gb89PkUFe97JuoCS8e74ltOu+A20ke6sSTKD1zpUc7tUGE7QdOoOYeCZL/PJ2qc0WN9d PrSORdDNAc3kLWz/bKIufgR8eJlUXoPcivzBw=|
|References:||<1374823420041-35002.post@xxxxxxxxxxxxx> <20130726115021.GO13468@dastard> <CAA+BczQesNL2VmFmrcBNKXcM-Sfx0bXkXPRP5xMx6=Bv+NWrUA@xxxxxxxxxxxxxx> <51F2CD8B.8080207@xxxxxxxxxxxxxxxxx> <CAA+BczQGYoJVL0twvz2GRhH30teFPSJOsKWtofbXBrom4_Q6hg@xxxxxxxxxxxxxx> <20130726205018.GM3111@xxxxxxx> <CAA+BczSpn7Cu2rZWJ9Q2b1-Xh0365R9ykGxKHHymtRm2Q7xCuA@xxxxxxxxxxxxxx>|
Is it safe to say that speculative preallocation will not be used if a file is opened read-only?
It turns out that the kafka server does indeed write lots of log files, and rotate them after they reach a max size, but never closes the files until the app exits, or until it deletes the files. This is because it needs to make them available for reading, etc. So, an obvious change for kafka might be to close each log file after rotating, and then re-open it read-only for consumers of the data. Does that sound like a solution that would pro-actively release pre-allocated storage?
On Fri, Jul 26, 2013 at 5:04 PM, Jason Rosenberg <jbr@xxxxxxxxxxxx> wrote:
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH 44/49] xfs: Reduce allocations during CIL insertion, Mark Tinguely|
|Next by Date:||Re: [PATCH 27/49] xfs: consolidate extent swap code, Mark Tinguely|
|Previous by Thread:||Re: understanding speculative preallocation, Jason Rosenberg|
|Next by Thread:||Re: understanding speculative preallocation, Ben Myers|
|Indexes:||[Date] [Thread] [Top] [All Lists]|