you or somebody here could answer
I built all
our office computers to Core 2
Duos last year and earlier this year and am really happy w/ the
these machines. I guess I sort of assumed that most applications could
take advantage of the two cores and speed things up a bit though. I
know that the main advantage here is that your processor isn’t SLAMMED
one application, you still have 50% or your resources to do other
you are running solutions on RISA or whatever the demanding program may
Although this is great, the one processor is actually slower than some
hot running single processors (3GHz+), so net processing time
is that good?
applications going to be written
to use multiple cores? Can that be done with your program? (if not,
when?) We use Vectorworks for drafting, love the program…but REALLY
wish they would take advantage of dual cores. Maybe I should write
I don’t think other progs other than your CAD’s or FEA’s really
need to accomplish this.
again….depending on how
efficiently the programs use the cores, our computers could go back to
slammed when we push solve…or render something.
Bill Polhemus wrote:
"The chances of there being a
that needs more than 4 GB of physical memory are pretty slim for the
decade or so."
Bill. Yes, the OS handles the address space. But, it's still
going to limit how much memory a 32 bit program is allowed to use.
are more removed from day to day
analysis work or who work on smaller structures always think that no
EVER use 4 Gigs of memory. I won't say that running into that limit
is common, but it happens way, way more often than you imply.
it's new "sparse solver", I'd say that people would contact
me at least once a month regarding that memory issue. Since many of
other common programs (RAM?, STAAD?) do not have a true sparse solver,
imagine that they run into the issue just as often as we used to...
for large models that require lots of plate elements.
got ASCE requirements for
quartering winds and eccentric earthquakes. Run all of these for
both strength and serviceability load combinations at the same time,
quickly get to the 150+ load combinations. For models with tens of
thousands of members and plates you'd be surprised how relatively easy
is to run into that memory limit.
Sent: Monday, October
Subject: Re: 64 bit
Josh Plummer wrote:
argument against going with a 64
bit system that nobody mentioned: Even if you have 32 Gigs of memory
your new system, your engineering applications will (most likely) not
to use more than that 3.5 or 4 Gigs!!
That application's address
space really isn't an
issue, though. The OS handles that. The application doesn't care where
loaded in memory just as long as it can play peacefully there.
The chances of there being a single application that needs more than 4
physical memory are pretty slim for the next decade or so.