R
Randy Thelen
Guest
I'm considering buying a new motherboard & processor to speed up my
Xilinx synthesis process.
My synthesis system is Xilinx Web PACK 6.1i running on Windows XP on a
machine with a 1.1GHz AthlonXP & 256MB of 266 DDR memory.
My synthesis times are sluggish. I'm strongly considering upgrading
to a faster CPU with faster RAM (specifically, the Athlon 64 3000+
with 400MHz DDR DRAM). I'm curious if you folks have experience with
upgrading your hardware for the purpose of speeding up synthesis work.
What processor & motherboard combination worked well for you?
I'm not interested in a religious war of Intel vs. AMD.
I'm just curious, in your experience, is the synthesis process made
faster by:
1) faster memory
2) faster CPU
3) faster frontside bus
4) more L2 cache
Yeah, yeah, all of the above. Sure.
Fundamentally, I'm curious about personal experiences with upgrades.
For example, if you upgraded your processor and/or motherboard, what
sort of build speed increase did you get?
Assume, for the purpose of this exercise, that the system isn't paging
to disk (if it were, more memory would be the answer to that problem).
I've used the Performance Monitoring tools to watch paging activity,
avg. disk queue lengths, and CPU % utilization. Paging is low (except
as the tools progress from one phase to another). Disk queue lengths
are low. CPU % utilization is pegged at 100%.
The sorts of things that can cause CPU utilization include:
1) The memory takes too long to respond to CPU requests (high memory
latency)
2) The CPU takes too long to execute the instruction stream (low
instruction-per-cycle count)
3) The front side bus doesn't have the bandwidth to satisfy the
demands of the CPU (for reading or writing data)
4) The CPU is thrashing with a small cache, over comitting the front
side bus/memory subsystem
I am also quite aware that there are folks with lesser hardware than
I've described doing amazing things. I understand, and I think that's
great. Usually I'm of the opinion to buy last year's technology to
save memory (yes, and I make purchases at the Good Will). However, in
this particular situation, I'm willing to throw a chunk of dough at
the problem. This is my personal hobby and I work on my FPGA projects
at home. My wife and I just had a baby and the little guy demands
(and gets!) a great deal of time. Therefore, each minute I get with
the development tools is important. Thus, I want to increase the
number of builds I get per evening (reduced build times means more
builds per unit time).
One last note, if there are other strategies folks have used for
reducing build times, I'm interested to hear them. Ideally, there's a
solution that involves no outlay of cash. My wife notes that
many applications are packaged with performance tuning notes.
Alternatetively, there may be another development package that I
should be using.
Xilinx synthesis process.
My synthesis system is Xilinx Web PACK 6.1i running on Windows XP on a
machine with a 1.1GHz AthlonXP & 256MB of 266 DDR memory.
My synthesis times are sluggish. I'm strongly considering upgrading
to a faster CPU with faster RAM (specifically, the Athlon 64 3000+
with 400MHz DDR DRAM). I'm curious if you folks have experience with
upgrading your hardware for the purpose of speeding up synthesis work.
What processor & motherboard combination worked well for you?
I'm not interested in a religious war of Intel vs. AMD.
I'm just curious, in your experience, is the synthesis process made
faster by:
1) faster memory
2) faster CPU
3) faster frontside bus
4) more L2 cache
Yeah, yeah, all of the above. Sure.
Fundamentally, I'm curious about personal experiences with upgrades.
For example, if you upgraded your processor and/or motherboard, what
sort of build speed increase did you get?
Assume, for the purpose of this exercise, that the system isn't paging
to disk (if it were, more memory would be the answer to that problem).
I've used the Performance Monitoring tools to watch paging activity,
avg. disk queue lengths, and CPU % utilization. Paging is low (except
as the tools progress from one phase to another). Disk queue lengths
are low. CPU % utilization is pegged at 100%.
The sorts of things that can cause CPU utilization include:
1) The memory takes too long to respond to CPU requests (high memory
latency)
2) The CPU takes too long to execute the instruction stream (low
instruction-per-cycle count)
3) The front side bus doesn't have the bandwidth to satisfy the
demands of the CPU (for reading or writing data)
4) The CPU is thrashing with a small cache, over comitting the front
side bus/memory subsystem
I am also quite aware that there are folks with lesser hardware than
I've described doing amazing things. I understand, and I think that's
great. Usually I'm of the opinion to buy last year's technology to
save memory (yes, and I make purchases at the Good Will). However, in
this particular situation, I'm willing to throw a chunk of dough at
the problem. This is my personal hobby and I work on my FPGA projects
at home. My wife and I just had a baby and the little guy demands
(and gets!) a great deal of time. Therefore, each minute I get with
the development tools is important. Thus, I want to increase the
number of builds I get per evening (reduced build times means more
builds per unit time).
One last note, if there are other strategies folks have used for
reducing build times, I'm interested to hear them. Ideally, there's a
solution that involves no outlay of cash. My wife notes that
many applications are packaged with performance tuning notes.
Alternatetively, there may be another development package that I
should be using.