I recreated a new development environment and recompiled the rsync code. The
posix_fallocate call worked exactly as expected, immediately creating a file of
the size passed to the function. I tested up to 300GB without issue. I must
have had something set up incorrectly in my development envi
> I can't reproduce this behaviour. I created a 40 Gigs file (haven't 77
> Gigs left) on my XP box using the posix_fallocate function (which, btw.,
> is basically just a single native NT call under the hood) and it takes
> roughly a few milliseconds.
I checked the dodgy app lists.none of those ar
On Nov 2 17:42, Rob Bosch wrote:
> I found on MSDN that Windows has the capfilealloc function in all Windows OS
> versions. This function was designed to create a preallocated capture file
> of a specified size. It seems like this would accomplish what cygwin needs
> with the posix_fallocate fun
cated than
that but thought it may provide a way to quickly preallocate the file.
Rob
-Original Message-
From: Rob Bosch [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 01, 2007 5:27 PM
To: 'cygwin@cygwin.com'
Subject: High CPU usage on posix_fallocate call - CVS version
W
When my compiled version of rsync is using the posix_fallocate function Im
getting significant CPU usage. The machine is a dual-core processor and Im
getting 20%-25% CPU utilization during the posix_fallocate call. Machine
stats Windows Server 2003 x64 R2, 4GB RAM (over 2.0GB free), fiber
con
5 matches
Mail list logo
