From: mahmoodn <nt_mahmood@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: RE: reduce compilation times?
Date: Fri, 30 Nov 2007 09:15:00 -0000 [thread overview]
Message-ID: <14042402.post@talk.nabble.com> (raw)
In-Reply-To: <EDC8DDD212FEB34C884CBB0EE8EC2D9103B25E0F@namailgen.corp.adobe.com>
>If your hard drive throughput is faster than your CPU, then you are correct
and it does not make any >sense.
>For example, if you are using a 25 MHz 68030 and a 15,000 rpm 8 GB cache
Seagate drive connected >through SCSI-3, the drive is probably able to
completely feed the CPU.
>However, if your hard drive throughput is slower than your CPU, then -j
makes sense.>
>For example, if your CPU is a single core Pentium 4 at 3.6 GHz, and your
hard drive is any ATA connected >IDE drive, then -j would help, since the
CPU would have many spare cycles to burn while waiting for the >hard drive
to feed it, so it could be busy working on another compiler concurrently.
I test with a core 2 and -j2 worked fine.... But I still do not know why it
does not work on p4.
Any way.... thanks
John (Eljay) Love-Jensen wrote:
>
> Hi mahmoodn,
>
>> I have single core, P4. So I think -j does not make any sense. Is it
>> right?
>
> If your hard drive throughput is faster than your CPU, then you are
> correct and it does not make any sense.
>
> For example, if you are using a 25 MHz 68030 and a 15,000 rpm 8 GB cache
> Seagate drive connected through SCSI-3, the drive is probably able to
> completely feed the CPU.
>
> However, if your hard drive throughput is slower than your CPU, then -j
> makes sense.
>
> For example, if your CPU is a single core Pentium 4 at 3.6 GHz, and your
> hard drive is any ATA connected IDE drive, then -j would help, since the
> CPU would have many spare cycles to burn while waiting for the hard drive
> to feed it, so it could be busy working on another compiler concurrently.
>
> HTH,
> --Eljay
>
>
--
View this message in context: http://www.nabble.com/reduce-compilation-times--tf4880765.html#a14042402
Sent from the gcc - Help mailing list archive at Nabble.com.
WARNING: multiple messages have this Message-ID
From: mahmoodn <nt_mahmood@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: RE: reduce compilation times?
Date: Fri, 30 Nov 2007 13:33:00 -0000 [thread overview]
Message-ID: <14042402.post@talk.nabble.com> (raw)
Message-ID: <20071130133300.Qn80ekwnrF1azX8HbLTyOo0FAG9LAcPtAP103rIRyww@z> (raw)
In-Reply-To: <EDC8DDD212FEB34C884CBB0EE8EC2D9103B25E0F@namailgen.corp.adobe.com>
>If your hard drive throughput is faster than your CPU, then you are correct
and it does not make any >sense.
>For example, if you are using a 25 MHz 68030 and a 15,000 rpm 8 GB cache
Seagate drive connected >through SCSI-3, the drive is probably able to
completely feed the CPU.
>However, if your hard drive throughput is slower than your CPU, then -j
makes sense.>
>For example, if your CPU is a single core Pentium 4 at 3.6 GHz, and your
hard drive is any ATA connected >IDE drive, then -j would help, since the
CPU would have many spare cycles to burn while waiting for the >hard drive
to feed it, so it could be busy working on another compiler concurrently.
I test with a core 2 and -j2 worked fine.... But I still do not know why it
does not work on p4.
Any way.... thank you
John (Eljay) Love-Jensen wrote:
>
> Hi mahmoodn,
>
>> I have single core, P4. So I think -j does not make any sense. Is it
>> right?
>
> If your hard drive throughput is faster than your CPU, then you are
> correct and it does not make any sense.
>
> For example, if you are using a 25 MHz 68030 and a 15,000 rpm 8 GB cache
> Seagate drive connected through SCSI-3, the drive is probably able to
> completely feed the CPU.
>
> However, if your hard drive throughput is slower than your CPU, then -j
> makes sense.
>
> For example, if your CPU is a single core Pentium 4 at 3.6 GHz, and your
> hard drive is any ATA connected IDE drive, then -j would help, since the
> CPU would have many spare cycles to burn while waiting for the hard drive
> to feed it, so it could be busy working on another compiler concurrently.
>
> HTH,
> --Eljay
>
>
--
View this message in context: http://www.nabble.com/reduce-compilation-times--tf4880765.html#a14042402
Sent from the gcc - Help mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-11-30 9:13 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 10:04 mahmoodn
2007-11-27 11:11 ` Andrew Haley
2007-11-27 11:15 ` mahmoodn
2007-11-27 11:30 ` Andrew Haley
2007-11-27 12:20 ` mahmoodn
2007-11-27 12:25 ` John Love-Jensen
2007-11-27 15:27 ` Tim Prince
2007-11-27 14:07 ` Andrew Haley
2007-11-28 9:01 ` mahmoodn
2007-11-28 12:11 ` John (Eljay) Love-Jensen
2007-11-30 9:15 ` mahmoodn [this message]
2007-11-30 13:33 ` mahmoodn
2007-11-27 15:48 ` Sven Eschenberg
2007-11-27 16:27 ` Andrew Haley
2007-11-27 18:51 ` Sven Eschenberg
2007-11-27 19:21 ` Andrew Haley
2007-11-27 20:43 ` Sven Eschenberg
2007-12-01 12:20 ` mahmoodn
2007-12-03 16:14 ` Andrew Haley
2007-12-04 11:23 ` mahmoodn
2007-12-04 12:19 ` Tom Browder
2007-12-05 7:44 ` mahmoodn
2007-12-05 10:24 ` Tom Browder
2007-12-05 10:29 ` mahmoodn
2007-11-27 13:48 ` John Love-Jensen
2007-11-27 16:07 J.C. Pizarro
2007-11-27 16:19 ` Brian Dessent
2007-11-27 16:26 ` J.C. Pizarro
[not found] ` <5abcb5650711270804o171e1facr565beec70314af75@mail.gmail.com>
2007-11-27 16:41 ` J.C. Pizarro
2007-11-27 16:46 ` Tom St Denis
2007-11-27 17:16 ` J.C. Pizarro
2007-11-27 17:46 ` Tom St Denis
2007-11-27 18:26 ` Wesley Smith
2007-11-27 19:35 ` NightStrike
2007-11-27 19:41 ` John (Eljay) Love-Jensen
2007-11-27 19:49 ` Tom St Denis
2007-11-28 9:19 ` Brian Dessent
2007-11-28 12:07 ` Tom St Denis
2007-11-28 12:35 ` Brian Dessent
2007-11-27 17:44 ` Vladimir Vassilev
[not found] ` <998d0e4a0711271310k657b791cy6ad5cc5721105f4c@mail.gmail.com>
2007-11-27 22:30 ` J.C. Pizarro
2007-11-28 7:57 Duft Markus
2007-11-28 12:01 ` J.C. Pizarro
2007-11-28 12:28 ` Tom St Denis
2007-11-28 12:49 ` Fabian Cenedese
2007-11-28 13:03 ` Tom St Denis
2007-11-28 12:52 ` J.C. Pizarro
2007-11-28 13:17 ` Tom St Denis
2007-11-28 13:40 ` J.C. Pizarro
2007-11-28 13:51 ` Tom St Denis
2007-11-28 13:59 ` Tom St Denis
2007-11-28 15:51 ` John (Eljay) Love-Jensen
2007-11-28 13:30 ` Ted Byers
2007-11-28 12:12 ` John (Eljay) Love-Jensen
2007-11-28 12:31 ` J.C. Pizarro
2007-11-28 12:39 ` Tom St Denis
2007-11-28 12:54 ` John (Eljay) Love-Jensen
2007-11-28 12:18 ` Tom St Denis
2007-11-28 13:09 ` Ted Byers
2007-11-28 12:36 Duft Markus
2007-11-28 13:25 Duft Markus
2007-11-28 13:26 ` Tom St Denis
2007-11-28 13:56 Duft Markus
2007-11-28 14:35 ` Tom St Denis
2007-11-29 0:23 ` Tim Prince
2007-11-28 16:06 J.C. Pizarro
2007-11-28 16:16 ` Tom St Denis
2007-11-28 16:34 ` J.C. Pizarro
2007-11-28 18:18 ` Tom St Denis
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=14042402.post@talk.nabble.com \
--to=nt_mahmood@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
/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).