public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] wxWidgets3.0
Date: Mon, 23 Nov 2020 19:34:00 +0000	[thread overview]
Message-ID: <AM6PR02MB3991AC7D8994EE5B3AAE38DEE7FC0@AM6PR02MB3991.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <AM6PR02MB39912413667F4FFC3B96FCD2E7FC0@AM6PR02MB3991.eurprd02.prod.outlook.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2276 bytes --]

On 23/11/2020 19:24, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 23/11/2020 19:16, ASSI wrote:
>> Hamish McIntyre-Bhatty via Cygwin-apps writes:
>>> That is strange if it's so much faster on your system.
>> I've checked again to be sure:
>>
>> Compile 41 minutes, install 7 (32bit) / 4 (64bit) minutes, packaging 5
>> minutes.
> Okay, wow that is a LOT quicker. I haven't timed mine precisely buts
> it's something like:
>
> Compile 2 hrs, install 40 minutes (64bit), 120 minutes (32bit),
> packaging probably like 5 minutes.
>
>>> Fortunately I have loads of memory so it's not too much of an issue
>>> for me. Most of the time on 32-bit Cygwin is spent stripping the
>>> executables, which is _way_ slower than on 64-bit Cygwin, by a factor
>>> of probably 3-4.
>> What's the disk based on?  I've recently switched to NVMe and while it's
>> not doing wonders compared to the SATA-SSD I've had before it has helped
>> to shave some time off the builds, generally in the order of 10…25% (for
>> gcc that means about half an hour so that's very welcome even if it
>> doesn't sound much).  Running a VM probably means you're running on a
>> filesystem image rather than a dedicated disk and that probably means an
>> extra slowdown anyway.  NVMe would enable you to make that overhead go
>> away, but it needs to be supported through the whole hypervisor / VM
>> stack to be effective.
> I have an NVME disk, but all my VMs (including this one) are on a SATA
> disk, and it's a Samsung QVO 1TB one that was cheaper but also slower
> (sustained write slows down to 80 MB/s eventually). Read is quick
> though. IIRC it's presented as SATA to the VM too.
>
> I'd better have a look at my configuration. Maybe do some disk and CPU
> benchmarks. This is in virtualbox so perhaps it's yet another problem
> with that, in the long list of problems I seem to have with virtualbox.
> The VM has 16GB of RAM dedicated to it, how does that compare to your
> system?
>
> Hamish

I think my fork speed is quite slow - when it prints out the "wxwidgets
has been installed, update LD_LIBRARY_PATH yada yada" messages during
install I can see it printing out the individual lines.

I don't know whether it was always that slow.

Hamish


[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-11-23 19:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 19:20 Hamish McIntyre-Bhatty
2020-10-17  0:21 ` Lemures Lemniscati
2020-10-17 13:17   ` Hamish McIntyre-Bhatty
2020-10-17 15:04     ` Brian Inglis
2020-10-19 15:31       ` Hamish McIntyre-Bhatty
2020-10-21 13:57         ` Hamish McIntyre-Bhatty
2020-10-21 17:17           ` Brian Inglis
2020-10-21 18:39             ` Achim Gratz
2020-10-27 11:53               ` Hamish McIntyre-Bhatty
2020-10-27 13:16                 ` ASSI
2020-10-28  2:21                   ` Hamish McIntyre-Bhatty
2020-10-28  8:40                     ` Achim Gratz
2020-10-30 19:39                       ` Hamish McIntyre-Bhatty
2020-11-11 15:15                       ` Hamish McIntyre-Bhatty
2020-11-11 17:36                         ` Hamish McIntyre-Bhatty
2020-11-12 18:00                           ` Hamish McIntyre-Bhatty
2020-11-21 16:52                             ` Hamish McIntyre-Bhatty
2020-11-21 21:56                               ` Brian Inglis
2020-11-22  9:43                                 ` Achim Gratz
2021-01-08 17:07                                   ` Hamish McIntyre-Bhatty
2021-01-08 17:15                                     ` Achim Gratz
2020-11-22  9:41                               ` Achim Gratz
2020-11-23 12:53                                 ` Hamish McIntyre-Bhatty
2020-11-23 15:26                                   ` ASSI
2020-11-23 16:18                                     ` Hamish McIntyre-Bhatty
2020-11-23 19:16                                       ` ASSI
2020-11-23 19:24                                         ` Hamish McIntyre-Bhatty
2020-11-23 19:34                                           ` Hamish McIntyre-Bhatty [this message]
2020-11-23 20:05                                           ` ASSI
2020-11-23 20:11                                             ` Hamish McIntyre-Bhatty
2020-11-24 10:15                                               ` Hamish McIntyre-Bhatty
2020-11-24 10:43                                                 ` Hamish McIntyre-Bhatty
2020-11-24 19:51                                                   ` Hamish McIntyre-Bhatty
2020-11-25 10:02                                                     ` Hamish McIntyre-Bhatty
2020-12-09 20:55                                                       ` Hamish McIntyre-Bhatty
2020-12-13 20:12                                                         ` Marco Atzeri
2020-12-14  9:46                                                           ` Hamish McIntyre-Bhatty
2020-12-14 20:21                                                             ` Marco Atzeri
2020-12-15  1:49                                                               ` Hamish McIntyre-Bhatty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM6PR02MB3991AC7D8994EE5B3AAE38DEE7FC0@AM6PR02MB3991.eurprd02.prod.outlook.com \
    --to=hamishmb@live.co.uk \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).