From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.107.17.87 with SMTP id z84mr4148374ioi.51.1508014504199;
        Sat, 14 Oct 2017 13:55:04 -0700 (PDT)
X-Received: by 10.157.94.7 with SMTP id d7mr175644oti.8.1508014504171; Sat, 14
 Oct 2017 13:55:04 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!l196no1302787itl.0!news-out.google.com!194ni1883itf.0!nntp.google.com!l196no1302785itl.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sat, 14 Oct 2017 13:55:03 -0700 (PDT)
In-Reply-To: <oqudb4$1e1b$1@gioia.aioe.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=92.221.111.106;
 posting-account=beIwHAoAAADU40dPBV1VR5DLW0gTDYxo
NNTP-Posting-Host: 92.221.111.106
References: <oqudb4$1e1b$1@gioia.aioe.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f78edbfc-e9f6-40da-ac3b-59b37255ae3d@googlegroups.com>
Subject: Re: How many CPU cores?
From: Tarjei Jensen <tarjei99@gmail.com>
Injection-Date: Sat, 14 Oct 2017 20:55:04 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Body-CRC: 996362805
X-Received-Bytes: 2028
Xref: news.eternal-september.org comp.lang.ada:48479
Date: 2017-10-14T13:55:03-07:00
List-Id: <comp.lang.ada>

If you are on windows, a "disk" might be your limiting factor. Use perfmon to monitor your logical disk drives. Go to Performance Monitor and add Physical disk -> % Idle Time for each available disk device.

It will tell you when Windows runs out of I/O for each disk. That is when % Idle Time for a logical disk is 0.

In Windows, logical disk I/O is a limited resource. You can have several logical disks pointing to the same physical device or use the same physical interface.

So in order to get I/O performance, you need to spread the load.

So having all your source code on the system drive (Usually C:) is a really bad idea.

If you are on something that is Unix-like, there is a number of options to get I/O statistics. Including the old faithful "sar". Determining how the system perfores will include a lot of interpretation of numbers.