X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9CDBF385741F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cs.umass.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.umass.edu To: cygwin From: Eliot Moss Subject: Curiosity about file access performance Message-ID: <00895c47-8df9-1f17-baac-0b3560de9d1c@cs.umass.edu> Date: Fri, 29 Oct 2021 10:35:08 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 Content-Language: en-US X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: moss AT cs DOT umass DOT edu Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "Cygwin" Dear Cygwiners - I think a lot of us know that fork() under Cygwin is slower than on Linux and have some grasp of why. But I have noticed that file access is rather lower under Cygwin as well. My "poster child" for this is running latex. I am working on writing a book, which includes a huge number of LaTeX style files and such. Under WSL1 (which has the same fork cost issues as Cygwin for similar reasons), reading the style files goes by in little more than the blink of an eye (about 1 sec), while on Cygwin it takes a little over 17 seconds. The time to process the body of the book is 23 seconds under WSL1 and 35 under Cygwin. So the total times are 53 seconds under Cygwin and 24 under WSL1. I believe the LaTeX installations are the same versions, and I get the same outputs. Both LaTeX's are 64 bit programs. There is not much forking here (at least I don't believe there is, but maybe there is under the cover for doing things with pdf figures or something), but a fair amount of file I/O. For many / most things, the Cygwin overhead is tolerable; for running this book, since I will be doing it over and over, it was worth investing in getting everything set up on WSL1. But it got me wondering as to why? Best wishes - Eliot -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple