This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Performance optimization in av::fixup - use buffered IO, not mapped file
On Dec 12 12:11, Christopher Faylor wrote:
> On Wed, Dec 12, 2012 at 12:06:08PM -0500, Ryan Johnson wrote:
> >It's painfully reproducible. It takes nearly two hours for a gcc
> >bootstrap compiler to configure the various bits of the next stage. It's
> >the same for emacs unexec (as OP reported).
>
> I'd like to see a small controlled test case which demonstrates the
> problem. If the claims here are all true then it should be very easy to
> demonstrate without resorting to bootstrapping the compiler.
>
> And, given my comment about setup.exe, I suspect that this isn't going
> to be as alarming an issue for the normal Cygwin user as it is for
> people who, e.g., rebuild their own compilers.
Which would speak for adding a "nosparse" mount option.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
- References:
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file
- Re: Performance optimization in av::fixup - use buffered IO, not mapped file