Bay 12 Games Forum

Dwarf Fortress => DF General Discussion => Topic started by: schm0 on November 06, 2007, 11:34:00 am

Title: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: schm0 on November 06, 2007, 11:34:00 am
I decided to make a thread to report all of the things that bring DF to it's knees for all you players out there. Please list your processor and memory specs, then note the activity or activities that slow down DF for you. This way, Toady can go through the list and hopefully speed things up for the next release.

What is your processor brand and speed?
How much RAM do you have?
Do you run faster on maps without running water?
Do you run faster on maps without magma?
Do you run faster with certain features turned on or off?
Do you run faster when certain tasks aren't being performed by your dwarves?
What do you slows down the game the most for you?

[ November 06, 2007: Message edited by: schm0 ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Tormy on November 06, 2007, 11:43:00 am
I have a 3GHZ P4 and 1 GB of RAM.
To be honest I have zero idea that what is causing the lag spikes.
I have like 60-70 FPS most of the time, however sometime I have a lag spike, the FPS is going down to ~20 for like 5-10 secs, and its going back to 60-70 after that. It aint happens very often but its still annoying when it happens.

[ November 06, 2007: Message edited by: Tormy ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Frobozz on November 06, 2007, 12:48:00 pm
Two reasons for me. First, I have to run the program through Wine since I'm on Linux. Second, weather. Weather eats up a good chunk of the frame rate. To help increase speed the most I simply turn off weather (last I knew it did very little at this point) and modify some settings in the init.txt file (I set FPS_CAP to 75 and G_FPS_CAP to 50). With those changes the speed, now maxed at 50, almost never drops below 40.

As to how Toady can fix these issues, there are two major ways I can easily mention off the top of my head. First, he can port DF to Linux. What little I talked to him about it indicated that it wouldn't be that much effort.

The second way is probably by far the hardest optimization of all - multithread the engine. Processor technology at this point is heading rapidly towards multiple cores for processing data and, while currently there are still reasonable increases in speed for individual cores, that is bound to slow down a good deal at some point. Tom's Hardware recently previewed a new CPU from Intel called Penryn. On the last page of that article they express the opinion that a version of it could be made with eight cores.

[ November 06, 2007: Message edited by: Frobozz ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: thvaz on November 06, 2007, 01:16:00 pm
I wish multithreading very much. Please Toady  :)
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: SwiftSpear on November 06, 2007, 01:17:00 pm
quote:
Originally posted by thvaz:
<STRONG>I wish multithreading very much. Please Toady   :)</STRONG>

If only modifying a piece of software to be multithread capable was as easy as just wishing for it.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: mport2004 on November 06, 2007, 01:31:00 pm
AMD Athlon 64 X2 dual core processor 6000+ 3.0 GHz
2046MB RAM
water seems to kill my fps
also im sure it dosent help that ive got a dual core
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Symmetry on November 06, 2007, 02:21:00 pm
quote:
Originally posted by SwiftSpear:
<STRONG>
If only modifying a piece of software to be multithread capable was as easy as just wishing for it.</STRONG>

If world wishes would were look threads like the this  :(

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: bremac on November 06, 2007, 03:11:00 pm
quote:
Originally posted by Frobozz:
<STRONG>First, he can port DF to Linux. What little I talked to him about it indicated that it wouldn't be that much effort.
</STRONG>

Wine isn't (or at least, shouldn't be) a major issue - wine is only a very thin layer remapping calls and reading PE files, so slowdowns due to it should only be O(1) with a c, hardly major loses; I'd expect maybe an increase of 0 to 1 FPS comparing native to wine, myself. Most of DF's speed is likely limited by the algorithmic complexity/cache miss rate of lookups, and the GPU.

I can't comment on what the real causes of non-feature slowdowns are, as I'm not the one with access to source and a profiler. Toady knows better than any of us what's really eating into time.

[ November 06, 2007: Message edited by: bremac ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Arven on November 06, 2007, 04:20:00 pm
I have a 2.7 ghz dual core cpu and 2 GB ram and have no lag or FPS spikes.
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Capntastic on November 06, 2007, 04:26:00 pm
3.4ghz processor and 2gigs of RAM, no lag except for the few minor bits (z-pathing, z-LOS) that are slowly being resolved.

Toady seems to know where most of the bottlenecks are, as it's mostly code that needs to be optimized.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Frobozz on November 06, 2007, 04:59:00 pm
quote:
<STRONG>Wine isn't (or at least, shouldn't be) a major issue - wine is only a very thin layer remapping calls and reading PE files, so slowdowns due to it should only be O(1) with a c, hardly major loses; I'd expect maybe an increase of 0 to 1 FPS comparing native to wine, myself. Most of DF's speed is likely limited by the algorithmic complexity/cache miss rate of lookups, and the GPU.</STRONG>

I haven't looked at Wine much I mostly just run it. But I'm going to assume that it isn't a direct one-to-one remapping of the calls. The only way that would be possible is if Linux had at least all the calls that Windows has. That isn't likely.

Why the GPU? The GPU has very little to do with this game. The most complex mode it has is to display a textured quad on the screen. Surely one simple texture isn't complex. Wouldn't even need to update that texture every frame either.

Also I happen to know Wine is slowing things down because I've already tested this system under Windows XP. If you think it might be my system in some way, let me give you some of my specs

Pentium D 805 at 2.66GHz per core on a 533MHz FSB
1GB DDR2-667 (only running at 533 thanks to the CPU)
GeForce 8600GTS with 256MB memory

Of course specs aren't necessary because, as I said, I've already tested under XP and Linux. There is a visible speed decrease. Oh and I am running official NVidia drivers before anyone asks. Believe it or not, I get more FPS under Linux than Windows typically.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Tormy on November 06, 2007, 05:10:00 pm
quote:
Originally posted by Arven:
<STRONG>I have a 2.7 ghz dual core cpu and 2 GB ram and have no lag or FPS spikes.</STRONG>

What FPS do you have on a 6x6 starting area at least after like 1 year has passed in the fortress?

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Vodalian on November 06, 2007, 06:07:00 pm
quote:
Originally posted by SwiftSpear:
<STRONG>

If only modifying a piece of software to be multithread capable was as easy as just wishing for it.</STRONG>


Multithread capable?  Uhm...   :roll:

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Dreamer on November 06, 2007, 07:09:00 pm
I have...

AMD Athlong(tm!) 64 Processor, 3400+ (Not sure what that means), 2.21 GHZ, 3 GigaBytes of RAM.  Maps with Running water creates brief periods of 'normal', and brief periods of 'space walking'.

I actually haven't played around too much with everything else, since I'm not too worried about the lag.  It's just odd.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Nukeitall on November 06, 2007, 08:46:00 pm
Particularly vicious processor slowdowns during excessive pathfinding, fluids, and my favorite, invasion pathfinding.

Ever been dual sieged? yeah.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: nagromo on November 06, 2007, 09:22:00 pm
quote:
Originally posted by Frobozz:
<STRONG>
I haven't looked at Wine much I mostly just run it. But I'm going to assume that it isn't a direct one-to-one remapping of the calls. The only way that would be possible is if Linux had at least all the calls that Windows has. That isn't likely.
</STRONG>

It doesn't need to be; it's still O(1). For some particular Windows function, Wine may have to translate from a Win32 data structure to an X11 data structure and call 3 shorter Linux functions, but it's still just a remapping that will take an extra 300 clock cycles (made-up example number).

Wine should give a constant slowdown for each Windows function called. The game uses lots of CPU on game logic and very little on rendering and interfacing. All of Wine's slowdowns should happen in the interfacing and rendering part of the code, which is very little of the total CPU time.

Unless Toady uses Windows-specific functions all over the game logic and inner loops (pointless/overly complicated), Wine will have much less slow-down on DF than it does on most Windows programs.

quote:
<STRONG>
Of course specs aren't necessary because, as I said, I've already tested under XP and Linux. There is a visible speed decrease. Oh and I am running official NVidia drivers before anyone asks. Believe it or not, I get more FPS under Linux than Windows typically.</STRONG>

So if you typically get more FPS on Linux, this indicates that Wine doesn't have a significant performance cost for DF.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: The13thRonin on November 06, 2007, 10:29:00 pm
The game is 'playable' at the moment but weather, path finding, temperature and fluids are all real killers at the moment. I'm confident Toady will find new and innovative ways to optimize his code so that we get the most out of our current technology.
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Frobozz on November 06, 2007, 11:17:00 pm
quote:
<STRONG>So if you typically get more FPS on Linux, this indicates that Wine doesn't have a significant performance cost for DF.</STRONG>

I worded that badly. I intended to indicate that I get more FPS under 3D applications and games.

 

quote:
<STRONG>I'm confident Toady will find new and innovative ways to optimize his code so that we get the most out of our current technology.</STRONG>

Toady is definitely a good programmer. But even if he finds innovative ways to optimize his code any performance increases achieved are likely to be offset quite a bit as he adds new features.

Multithreading is really one of the better ways to go. Not every has multiple cores right now - but what about when the game hits 1.0? A good nine months passed between updates and that was only a minor version increase. I suspect by the time the game is considered beta that the majority people will possess multiple core systems.

Of course another possibility occurred to me. If the parts involving the terrain, temp, and weather could be made to work through multiple threads then why not make a version that uses the GPU to do the calculations?

[ November 06, 2007: Message edited by: Frobozz ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Zemat on November 06, 2007, 11:34:00 pm
Seeing the huge boost in performance in some details that are common both in pre-Z-DF and post-Z-DF and then the later boost from 32a to 33a I guess Toady is really getting the hang on how to optimize the code. I hope there's still a lot of room for improvement in performance before requiring a full rewrite. Because I don't want Toady spend one or two years just rewriting the code instead of adding new features.

Also, something I learned from my stints as a software engineer (...shudders) is that sometimes rewrites come too early and improve nothing. And I say this as a compulsive software rewriter. Most of the time the greatest performance issues are just bug-related and can be fixed by just moving or erasing a line of code of two.

[ November 06, 2007: Message edited by: Zemat ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Bien on November 07, 2007, 04:01:00 am
I got a P4 1.7 GHz CPU, 633 MB RAM, running with temperatures on and I'm still maxing my FPS cap of 100, lucky me, I guess.
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: The13thRonin on November 07, 2007, 06:32:00 am
quote:
Originally posted by Bien:
<STRONG>I got a P4 1.7 GHz CPU, 633 MB RAM, running with temperatures on and I'm still maxing my FPS cap of 100, lucky me, I guess.</STRONG>

With a huge map including magma though? I doubt it.

NINJA EDIT - I believe that this lag sucks  :(. I foresee two outcomes. Toady will optimize the code OR we'll just have to wait until stronger/faster processors come out that are able to handle Dwarf Fortress in all its epic scale glory.

[ November 07, 2007: Message edited by: The13thRonin ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Guilliman on November 07, 2007, 08:07:00 am
Detailed report of my findings and observations:
I run a AMD x2 5800 dualcore ofc
2gig of ddr2 ram, 800mhz


My findings:

FPS drop when
-creatures (inc dwarfs) run over each other but attempt to go diagonally.
-Huge differences in cliff heights (I noticed a small map with rather big cliff differences (4-5) has my maxed out fps of 250) while others have a higher cliff variation i run aground to 40fps. I'm thinking in the area of amount of different stone, the 250fps area had only 3 different stone layers and 3 sand ones.
-Water has no affect on fps, not for me at least, apart from flooding something with a 100x100x10 reservoirs, and even then, the fluid algorithm is very smooth.
-stairs/ramps cause a huge drop in fps, My guess is, dwarfs attempt to go diagonally up or down (i build multiple wide stairs/ramps)
-I still think there's a connection with lower fps when i look trough more starting zones (like toady mentioned he fixed it. I think a part is still there.)


So far thats on the top of my head what i came to find.


edit for spelling
edit 2 for this:

Perhaps toady can change the game so that it used the graphic card to do all the path finding algorithms. Or at least some of them, with an option to scale/put it on off in the ini.


[ November 07, 2007: Message edited by: Guilliman ]

[ November 07, 2007: Message edited by: Guilliman ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: schm0 on November 07, 2007, 09:33:00 am
Well, I guess it's my turn:

My System Specs say:
AMD Athlon 64 Processor 3400+, 1.8 Ghz
896 MB (1 GB> ) RAM

(I downloaded a program and it analyzed my computer and said I had 2.4 GHz. Perhaps my processer is overclocked?)

My first map had a magma vent. As soon as I had about 40 dwarves, I was averaging about 35 FPS. On my latest map, I have a brook and no surface magma and I average 60-70 FPS but haven't had my first immigration.

On both maps, I am building underground sewers that will be used to drain some of the local lakes and hook into the brook for a permanent water source for farming. Draining the lakes does create lag, but as soon as the water sources are settled, they jump back up. This is to be expected. I think the magma vent causes more FPS lag because it is trying to calculate any possible shifts every so often for X amount of Z-axis layers. In the case of the former fortress, it went down 18 levels. That's a lot of fluid to calculate, but is only about 30 FPS less than without magma altogether. Perhaps a magma vent should need no calculations until tiles surrounding it are modified or accessing the fluid itself has begun?

I also think that graphic card and multithread support should be implemented as soon as possible to take the load off the CPU. I think a lot of us will find a huge increase in FPS once this is supported.

[ November 07, 2007: Message edited by: schm0 ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: hactar1 on November 07, 2007, 09:59:00 am
I've played on 2 computers... an Athlon64 3500+ with 1G of ram, and a Core2 Duo Xeon at 2.66 GHz per core, 2 GB ram.  The Athlon doesn't handle large maps well, at least not always.  The Xeon handles most everything well enough.

The only thing I've noticed that slows me down consistently is defining a meeting area or sculpture garden.  It's not really a performance-specific issue though, but about half my dwarves and every single stray animal will instantly descend upon the new meeting area and turn it into a dwarven moshpit of laggy doom.  It was even worse in .32a when prone creatures caused lag.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Mover#005 on November 07, 2007, 12:09:00 pm
2,4 GHz Core 2 Duo & 2 GB RAM & Linux WINE

No lag (as long as I don't do stupid things like pike a huge area in a lively region etc.)

Adventure Mode is nearly unplayable, through

quote:

...

The second way is probably by far the hardest optimization of all - multithread the engine. Processor technology at this point is heading rapidly towards multiple cores for processing data and, while currently there are still reasonable increases in speed for individual cores, that is bound to slow down a good deal at some point. Tom's Hardware recently previewed a new CPU from Intel called Penryn. On the last page of that article they express the opinion that a version of it could be made with eight cores.

[ November 06, 2007: Message edited by: Frobozz ][/QB]


Jesus... who even does NEED something like this?

[ November 07, 2007: Message edited by: Mover#005 ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Mover#005 on November 07, 2007, 12:20:00 pm
*please delete*

[ November 07, 2007: Message edited by: Mover#005 ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Mover#005 on November 07, 2007, 12:21:00 pm
As an afterthought, I think you can screw up your game big time performance-wise with strange Fortress-layouts. I myself have written a fair share of pathfinding-algorithmns and finite state machine AIs and some designs which I see here or in the maparchive give me toothaches just looking at them. Alllthough I can't say how toadys engine works, some Pointers maybe (and please take them with a grain of salt):

1. Use the new Z-Axis. don't build a large fortress on just one Level. It isn't good for your efficency of the fort and pathfinding has to find a way from one end to the other.

2. Avoid open Spaces in your designs. more open titles = more possible Pathnodes.

3. Avoid locked doors and other toggleable blockages. I have the feeling they piss the pathfinder off big time if not used correctly.

4. Use Traffic-zones. Your dwarfs may find the best and shortest path anyways but they algorithm will thank for your help with less intensive cpu-hogging if you point out the clearly best titles.

I'm sure someone with the right background can add a few tips.

[ November 07, 2007: Message edited by: Mover#005 ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Trukkle on November 07, 2007, 06:40:00 pm
I'd love it if flows 'slept'. Having a whole load of 5s and 6s zooming around idefinatly after making a large pool can't be processor friendly. Perhaps making pools even out to the most common of the two numbers instead of jiggling them around in a constant effort to level the surface?

My computer's getting old, but if I could find the parts, I'd upgrade it to it's technical limit before buying a new one.

Athlon 2400+ (2GHz)
1.5 GB RAM
Windowed, no graphics, [G_FPS_CAP:10]

Dwarf mode, I chug when hauling a lot, even when there's a straight line from the thing to be hauled, to the space it's being hauled to and when I use pumps, even when off screen. Adventure mode is pretty impossible to play due to slowdown and crashes when trying to visit a fortress site, but I've yet to find a pattern to that.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Frobozz on November 07, 2007, 07:01:00 pm
quote:
Originally posted by Trukkle:
<STRONG>My computer's getting old, but if I could find the parts, I'd upgrade it to it's technical limit before buying a new one.</STRONG>

Who made your motherboard and what model is it? If you're using Socket A then you'll be hard pressed to find a faster processor - AthlonXPs used are mostly the same price as they were new and often more money than simply buying a new board and dual core processor.
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Trukkle on November 07, 2007, 08:04:00 pm
quote:
Originally posted by Frobozz:
<STRONG>
Who made your motherboard and what model is it? If you're using Socket A then you'll be hard pressed to find a faster processor - AthlonXPs used are mostly the same price as they were new and often more money than simply buying a new board and dual core processor.</STRONG>

(ASROCK K7NF2-RAID, if you're interested)
I've just come back from researching just that, and yeah. Processors aren't available, or if they are they're still at their 2003 prices :/
Looks like I'll be saving up for a whole new PC. I can run Bioshock fine and not feel the need to upgrade, but Dorfs bring me to my knees, wallet-in-hand.
Damnit Toady >:(

Missed it in my spec post, so: Average FPS of 45 with around 40 beardy, foul smelling, blood/mud/water/vomit soaked, ale quaffing, Elf kicking Dwarves, 10 tame animals and no surviving wildlife.

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Frobozz on November 08, 2007, 02:15:00 am
I've posted this in one other spot too, but if you want to save the most money I'd go with the ASRock 4CoreDual-SATA2 board. Supports Socket 775 so you could go with a $75 Pentium Dual-Core or a more expensive Core 2 Duo as well as DDR/DDR2 and AGP/PCI-express. The PCI-express runs at 4x speed and Jaqie mentioned something about power limitations. You'll want to check the manufacturer page.
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: termitehead on November 08, 2007, 04:16:00 pm
Remember it's not straight hardware you have to think about.  Sure you might have 4gig ram quad core rig.  But if you never defrag, have shit-tons of spyware, are running a dozen other processes, and so on...  you're gonna get shit lag.  I know a lot of people who have better pc's compared with my hardware but mine runs a lot better because I take care of it.  It's like any other game which requires decent hardware, minimize the number of processes you have running and keep a nice and clean environment - then start talking about hardware.
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Nukeitall on November 08, 2007, 05:31:00 pm
I think we're all overlooking the fact that Dwarf Fortress is no Crysis. It's too alpha to even consider performance.
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Frobozz on November 08, 2007, 05:58:00 pm
quote:
Originally posted by termitehead:
<STRONG>But if you never defrag, have shit-tons of spyware, are running a dozen other processes, and so on...  you're gonna get shit lag.  I know a lot of people who have better pc's compared with my hardware but mine runs a lot better because I take care of it.</STRONG>

Yes quite true unfortunately. Its one of the reasons people end up having to redo Windows every few months. And its also one of the reasons I totally dropped Windows (even though I had commercial tools like Diskeeper running in the background defragmenting during system idle periods) for Linux.

Regardless upgrading hardware still has a sizable impact. Especially if you go from an AthlonXP to Pentium Dual-Core/Core 2 Duo. If anything the spyware will have an additional core to hog and thus free up resources for Dwarf Fortress.  :D

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: mizipzor on November 08, 2007, 06:18:00 pm
I have a core2due running at 2.66Ghz and 2Gb ram. Running DF through wine in Kubuntu. But the fps is silly, Its usually around 10, maxing at 25 at times when nothing is going on (when Im starting out that is). And saving all the units after generating a world took a hilarious amount of time.

But getting this low performance in linux make me suspect that something is wrong with my settings. In windows Im usually at 100.

Edit: After installing proper graphics driver the fps is rocksteady at 75, I have it capped at that, gonna try raise it later.

[ November 08, 2007: Message edited by: mizipzor ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Frobozz on November 08, 2007, 11:17:00 pm
quote:
Originally posted by mizipzor:
<STRONG>But getting this low performance in linux make me suspect that something is wrong with my settings. In windows Im usually at 100.</STRONG>

Like I said earlier, I think Wine is eating up the processing time. Maybe it is having to rework how Dwarf Fortress is doing something behind the scenes in order for it to work perfectly. Either way I think porting the game would remove a lot of the issue.
Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Trukkle on November 10, 2007, 05:23:00 pm
quote:
Originally posted by termitehead:
<STRONG>Remember it's not straight hardware you have to think about.  Sure you might have 4gig ram quad core rig.  But if you never defrag, have shit-tons of spyware, are running a dozen other processes, and so on...  you're gonna get shit lag.  I know a lot of people who have better pc's compared with my hardware but mine runs a lot better because I take care of it.  It's like any other game which requires decent hardware, minimize the number of processes you have running and keep a nice and clean environment - then start talking about hardware.</STRONG>

Aaaaaaaaaand returning late once again.
Yep, I completely agree. I take care of my machine in just that manner, and my windows installs usually outlive my case fans because of it. There are new games out now (Not Crysis) that run better and a lot more reliably on my supposedly ancient setup than they do on current hardware. The problem is, it's never going to be possible to make it run any better in it's current incarnation. My processor is letting me down.

Can anyone get me up to speed on the current state of Intel? Comparative speed, heat tolerances, if they're still only doing 32bitx2, instead of true 64bit? Whether I'd need to get Vista (not happening)
I've been an AMD diehard for so long I forgot why I started. That's the only qualm I had with the board mentioned above. I'd gladly take this to email, PM or IM (check my profile)

[ November 10, 2007: Message edited by: Trukkle ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Frobozz on November 10, 2007, 06:45:00 pm
quote:
<STRONG>Can anyone get me up to speed on the current state of Intel? Comparative speed, heat tolerances, if they're still only doing 32bitx2, instead of true 64bit?</STRONG>

The article on Penryn on Tom's Hardware pretty much hints as to the direction they're heading. It seems they're into shrinking, speeding up, and reducing the power consumption of individual transistors. And they pretty much appear to be doing quite well at it.

I don't honestly think 64-bit is needed at this point. The only real advantage I see to it is more memory per program but I haven't run across too many programs that use more than 2GB. Specialty programs will always need it sure but you won't be running those programs on cheap processors (aka Core 2 Duo).

 

quote:
<STRONG>I've been an AMD diehard for so long I forgot why I started. That's the only qualm I had with the board mentioned above. I'd gladly take this to email, PM or IM (check my profile)</STRONG>

I was somewhat into AMD myself - part of the reason I went with AthlonXP. But these days I'm into whatever gives me the most performance for my money.

[ November 10, 2007: Message edited by: Frobozz ]

Title: Re: REPORT FOR TOADY: CPU and Memory Hogging -- What is slow
Post by: Lactose on November 10, 2007, 09:48:00 pm
delete

[ November 10, 2007: Message edited by: Lactose ]