Hi,

Ruby and the glibc the kernel etc are doing buffering already. 
There is usually no need for explict buffering from ruby.

You can test this for yourself, try to write the same string for a
million time in a loop. Not each write triggers a disk transaction.

Regards,

Markus 


On Thu, May 12, 2011 at 09:58:36PM +0900, Yoann M. wrote:
> Hello,
> I have data to process and to write into files progressively. The data
> files are in the end very large, but I append to them small strings. I
> suppose buffering the strings before apending to the file would be
> faster. I don't need the files to be written before the end of the whole
> process (i.e. I don't use their content).
> 
> I've searched for info about how File buffer its data but it seems we
> can not configure anything about this, did I miss something ?
> My first idea was to buffer everything myself, appending lines to a
> string, or an array of strings and write when I reach a big enough
> amount of data. But if File uses a buffer anyway, it would be a waste of
> time I suppose ?
> Do you have any advice to optimize the writing of large files ?
> Thanks !
> 
> -- 
> Posted via http://www.ruby-forum.com/.
>