Rob Bosch wrote:
> I took a stab at modifying the preallocate.diff patch file replacing it with
> ftruncate (attached). Do you think the file looks OK for Linux (obviously
> cygwin should use posix_fallocate)? I replaced posix_fallocate with
> ftruncate and also removed the check for HAVE_POSIX_F
I took a stab at modifying the preallocate.diff patch file replacing it with
ftruncate (attached). Do you think the file looks OK for Linux (obviously
cygwin should use posix_fallocate)? I replaced posix_fallocate with
ftruncate and also removed the check for HAVE_POSIX_FALLOCATE.
Maybe this sh
Matt McCutchen wrote:
> I notice that the Linux kernel 2.6.23 has gained a system call
> "fallocate" that preallocates at the filesystem level like Cygwin's
> implementation of posix_fallocate; thus, preallocation may become (at
> least slightly) helpful on Linux. Unfortunately, neither ext2 nor
>
> Attached is the C++ source for a simple program "allocate" to allocate a
> file. Call the
> program like "./allocate thefile 770".
Now that was fun. I was creating 300GB files with no fragmentation in less
than 1/2 a second! Seriously, the performance using the program was identica
On Sun, 2007-11-18 at 18:10 -0700, Rob Bosch wrote:
> Matt, I have absolutely no programming skills for developing my own
> program! I'd be happy to compile and test a program however.
Attached is the C++ source for a simple program "allocate" to allocate a
file. Call the program like "./alloc
Matt, I have absolutely no programming skills for developing my own program!
I'd be happy to compile and test a program however.
Are you going to put the fix for the preallocate patch in the 3.0 next
pre-release or release?
I'm pretty sure the function is being called properly since I see
On Mon, 2007-11-05 at 06:25 -0700, Rob Bosch wrote:
> When I use the preallocate patch and create a 77GB file using the function I
> get a CPU spike on the server-side.
I don't think reproducing the CPU spike on Linux will be meaningful
because Linux treats posix_fallocate differently from Cygwin
When I use the preallocate patch and create a 77GB file using the function I
get a CPU spike on the server-side. The spike lasts about 20 minutes and
uses about 20%-25% of the cpu associated with the rsync instance creating
the file. The spike is directly linked to the time it takes to create the
