Re: [DUG] Processor speeds and the need for concurrency

Phil Middlemiss Sun, 07 May 2006 14:26:45 -0700

I think they should throw more money at making disk access faster or, more realistically, viable alternatives - for us it is definitely the biggest bottle neck. Solid state is not commercially viable for large storage sizes yet (It's certainly cheaper than it used to be but can't be compared to conventional hard drives for cost).

I guess we could squeeze a little bit more of multiple core CPUs, but more/cheaper RAM, faster storage access are the real performance drivers for mapping/GIS software.

Cheers,
Phil.

[EMAIL PROTECTED] wrote:

Richard wrote:

Concurrency is something that most people who have written web
applications know they have to deal with.


Correct, it's old news in that area. But nonetheless real work,
depending on how well the framework you're using supports it.


The difference implied by the article quoted is that more
applications and hence developers will be running up against real
performance bottlenecks in future, and will have to find ways to deal
with them. Not just Phil Scadden and all us web developers <g>.

want. I don't see a huge impact here except for gamers and processor
intensive apps like graphics & number crunching?


Hmmm, an hypothesis. What do others think? Bags of room on the upside
for most of what you do?

cheers,
peter


_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi

begin:vcard
fn:Phil Middlemiss
n:Middlemiss;Phil
org:Vision Software, MTS Ltd
email;internet:[EMAIL PROTECTED]
title:Project Leader
tel;work:+64 7 3480001
tel;cell:+64 27 4592648
x-mozilla-html:TRUE
url:http://www.tumonz.co.nz
version:2.1
end:vcard

_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi

Re: [DUG] Processor speeds and the need for concurrency

Reply via email to