On 02/26/2015 02:18 PM, Robert Goulet wrote:
turns out to be 5000+ file open/close
Good catch! It looks like it's been that way since manifest generation
was first added here:
ENH: When installing project, write manifest
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=99feab35
I've
Great, let us know if the test is clean! Cheers!
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Thursday, February 26, 2015 3:13 PM
To: Robert Goulet; Joshua Clayton
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] cmake install command expected
consider it for CMake 3.2!
Thanks!
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Tuesday, February 24, 2015 10:07 AM
To: Robert Goulet; Joshua Clayton
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] cmake install command expected performance?
On 02/24
: Monday, February 23, 2015 9:28 PM
To: Robert Goulet
Cc: Nils Gladitz; cmake-developers@cmake.org
Subject: Re: [cmake-developers] cmake install command expected performance?
On Linux reading the input file would still be cached on subsequent runs even
if you remove the destination folder, and writing
On 02/24/2015 09:51 AM, Robert Goulet wrote:
takes 50+ seconds for cmake to realize that all files don't need
to be copied
It's comparing the time stamps of every corresponding file.
On many filesystems that is faster than the actual copy.
Perhaps the log spam for every file in the console is
On 02/24/2015 10:03 AM, Robert Goulet wrote:
Yes comparing timestamp is the way to go, but why is it so slow in cmake?
I've never observed that being slow in practice.
You'll have to profile CMake while running in this case, or add
some print statements with high-precision timestamps to see
this part is
taking the most amount of time.
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Tuesday, February 24, 2015 9:57 AM
To: Robert Goulet; Joshua Clayton
Cc: cmake-developers@cmake.org
Subject: Re: [cmake-developers] cmake install command expected performance
-developers] cmake install command expected performance?
On 02/24/2015 10:03 AM, Robert Goulet wrote:
Yes comparing timestamp is the way to go, but why is it so slow in cmake?
I've never observed that being slow in practice.
You'll have to profile CMake while running in this case, or add some print
On 02/23/2015 04:13 PM, Robert Goulet wrote:
I’m running into an issue were using the CMake install command to copy a
directory with over 5000+ files (slightly over 1GB of data) takes a lot
more time than doing a simple copy. On an SSD drive it takes 0.2 seconds
to copy, while it takes about 56+
...@gmail.com]
Sent: Monday, February 23, 2015 10:37 AM
To: Robert Goulet; cmake-developers@cmake.org
Subject: Re: [cmake-developers] cmake install command expected performance?
On 02/23/2015 04:13 PM, Robert Goulet wrote:
I'm running into an issue were using the CMake install command to copy
10 matches
Mail list logo
