64-bit games or multi threaded games

rcf1987

2[H]4U
Joined
Aug 9, 2004
Messages
3,759
I figured I sparked up a conversation so what would be better games that are 64-bit or games that are multi threaded?
 
64 bit Vista DX10 multithreaded games have my vote going forward.
 
multi-threaded, since it's more of a paradigm shift. Considering that you can easily have a compiler product a 64-bit game for you, but the developer needs to make something multi-threaded, it's clear that moving towards multi-threaded games is likely to be more complicated, but likely with higher rewards.
 
penguin said:
I vote multithreaded
I'm not a programer.... but I've read that the big problem taking full advantage of the new Xbox and PS3 is that type of programing is a nightmare.
 
I don't see why multithreading a game would be a programming nightmare , im only done my first year inprogramming though o.0 so who knows
 
Kendrak said:
I'm not a programer.... but I've read that the big problem taking full advantage of the new Xbox and PS3 is that type of programing is a nightmare.

One does have to remeber that PS3 expecially, but XBox360 to an extent as well, are not your typical multiprocessor systems.
Developing for a dual or quad core PC bears little resemabalance to developing for PS3 or even realy making the best possible use of the XBox's hardware either.


Digital Viper-X- said:
I don't see why multithreading a game would be a programming nightmare , im only done my first year inprogramming though o.0 so who knows

Imagine you've got a dozen different tasks to do, basically all of them requiring results and input from at least one other task. Arrange them in such a way that you can do as many in parallel as possible while minimizing the number of times individual tasks have to talk to each other.

Some games lend themselves to threading fairly well (4x turn based games where each AI player gets its own thread to 'think' while the human player makes his/her move), but most of the time it's a laborious task to achieve anything near an optimial design for threading with complex interactions and dependancies between almost all aspects of a game engine.
It's certainly not that it can't be done, and done effectively (at least over two or three cores for sure), it's that it's rather hard. Certainly nothing like media encoding where breaking the task into threads is almost trivial.
 
Multithreaded games would benefit more than 64 bit, for sure.

Multithreaded programming is a bitch. It is extremely hard to write good code for. Viper, what language are you using? Java does not have real threads (I am taking a guess this is what you're learning considering the trend in colleges and high schools). Multithreaded programs will often have 'shared resources' that both threads will eventually have to access. They cannot be accessing it at the same time. More problems involved with the timing of the threads. etc. etc. etc.


umm, but yeah. let's see some multithreaded games! :D
 
multi-threaded! but ya 64bit will be easier to adopt just look at HL2 valve already added 64bit support but no multi threaded support as that require a complete engine rebuild i think.
 
64 bit games will only allow more memory use - beyond 4gb.

That's it folks.

64 bit games does not mean more speed. Some 64 bit applications actually run slower than their 32 bit counterparts..

People with a single core CPU will so see no benefit from multi-threaded games either.
 
LordBritish said:
64 bit games will only allow more memory use - beyond 4gb.

That's it folks.

64 bit games does not mean more speed. Some 64 bit applications actually run slower than their 32 bit counterparts..

People with a single core CPU will so see no benefit from multi-threaded games either.
so running in 64-bit mode doesn't allow the CPU to add 2 64-bit numbers as one instruction rather than two?
 
drizzt81 said:
so running in 64-bit mode doesn't allow the CPU to add 2 64-bit numbers as one instruction rather than two?

Adding 2 numbers has always been a single instruction - even in the 16 bit days. Am I missing something here?
 
LordBritish said:
Adding 2 numbers has always been a single instruction - even in the 16 bit days. Am I missing something here?
Yes you are. Really big numbers have to be broken up into multiple tasks since they can not fit in the register space.
 
LordBritish said:
Adding 2 numbers has always been a single instruction - even in the 16 bit days. Am I missing something here?
ok, i am not sure how to word it:
The number of instructions cycles for a ADD command depends on the size of the two operands as well as their location (register etc.). Considering that a 64-bit operand does not fit into a 32-bit size register, one could consider that such an operation would be faster on a 64-bit arch.
 
vortexpud said:
Far Cry in 64 bit mode is pretty :D

Look folks, I'm not dissing 64 bit games or applications in general but a lot of peolpe think that 64 bit games are inherenlty faster, better looking, or just better in general.
 
drizzt81 said:
ok, i am not sure how to word it:
The number of instructions cycles for a ADD command depends on the size of the two operands as well as their location (register etc.). Considering that a 64-bit operand does not fit into a 32-bit size register, one could consider that such an operation would be faster on a 64-bit arch.

I understand that but that does not equate to faster applications - just more precise numbers.
 
Least said:
Multithreaded games would benefit more than 64 bit, for sure.

Multithreaded programming is a bitch. It is extremely hard to write good code for. Viper, what language are you using? Java does not have real threads (I am taking a guess this is what you're learning considering the trend in colleges and high schools). Multithreaded programs will often have 'shared resources' that both threads will eventually have to access. They cannot be accessing it at the same time. More problems involved with the timing of the threads. etc. etc. etc.


umm, but yeah. let's see some multithreaded games! :D

I agree multithreading is very hard on a programming level. Digital - One year of programming probably doesnt even touch multithreading huh? Its not easy. Imagine you doing laundry. You have 5 loads of laundry to do. You have 3 washers/dryers. So if you do the first three simulatniously and the next 2 simultaniously thats faster than doing 5 spereate loads right? Oh I forgot to mention that you only have 1 power outlet and 1 washer/dryer hookup. Good luck making doing your laundry "multithreaded". :)

Least - I know a little Java but havent used threads in Java. Why do you say that "Java doesnt have real threads"? Just wondering.

To stay on topic - I think it would beneficial to see multithreaded games instead of 64 bit games.
 
LordBritish said:
I understand that but that does not equate to faster applications - just more precise numbers.
Not if you are dealing with intergers.
 
LordBritish said:
If you think about it, a GPU and a CPU is sort of like multi threading :)

No, that's serial processing, not parallel ;)

My vote goes to multithreaded games. A much larger performance increase can be found there, but it's much more work too.
 
drizzt81 said:
ok, i am not sure how to word it:
The number of instructions cycles for a ADD command depends on the size of the two operands as well as their location (register etc.). Considering that a 64-bit operand does not fit into a 32-bit size register, one could consider that such an operation would be faster on a 64-bit arch.

But then one comes out of their dreamworld and realizes that adding two 64-bit integers is INCREDIBLY RARE.

Floating-point numbers as large as 80 bits, on the other hand, have been supported for years. The Athlon 64 will not process them any faster in 64-bit mode.

The major speedup, if any, comes from the 8 extra architected registers.

As for the original thread topic, I say multithreaded all the way. 32-bit games can run under Windows-on-Windows emulation layer fine, so you can have your 64-bit OS. That, and multiple threads will allow for much larger performance gains once all chips have 2 or more processors.
 
LordBritish said:
64 bit games will only allow more memory use - beyond 4gb.

That's it folks.

64 bit games does not mean more speed. Some 64 bit applications actually run slower than their 32 bit counterparts..

People with a single core CPU will so see no benefit from multi-threaded games either.
you're missing one VERY important thing:

x86-64 doubles the number of integer registers (along with a few other things). that alone should lend itself to a reasonable boost in performance if properly optimized for. ;)
 
64 Bit is another one of those things whos benefits will show over time. This is just the first step in forward thinking technology growth. In a few years we will look back at 32bit just as much as we would at 16 today. One visual way I can think of 64 bit was a presentation of HDRI for ps3. The 64 bit render had much better lighting range. So I guess that means more data, more detail, more info.
 
(cf)Eclipse said:
you're missing one VERY important thing:

x86-64 doubles the number of integer registers (along with a few other things). that alone should lend itself to a reasonable boost in performance if properly optimized for. ;)

I'm pretty sure it is actually exponentially larger, not double.

Java threads (or timers) will run sequentially (simulated running at the same time) regardless of what type of system used.
 
(cf)Eclipse said:
you're missing one VERY important thing:

x86-64 doubles the number of integer registers (along with a few other things). that alone should lend itself to a reasonable boost in performance if properly optimized for. ;)

register renaming makes this less of an issue than you might think.
80 registers for in flight integer insructions, and 32 used to represent the architectual registes (16 soruce, 16 dest to minimize the impact of false dependancies. You don't have to evict something from the destination reg to load something the source reg).
 
Sabrewulf165 said:
Why not games that are 64-bit *AND* multi-threaded :confused:


lol i was about to say that hell i think i will

I WANT BOTH :D
 
just thought i would bring this up. decided to check the games i have installed to see how many threads they use and here is what i found.


WoW - 22 Threads
Track Mania Nations - 15 Threads
RoN:RoL - 9 Threads
Live For Speed - 7 Threads





seems to say to me games are already multithreaded, possibly they need to be optimized?
 
Ok gonna clear a few things up here. Multithreaded would be much faster, given more than one core for processing. 64bit would just make things larger, more accurate. A 64 bit CPU will do almost nothing for the performance in games.

I might be wrong but my understanding of the x86-64 CPUs was that they do nothing but 32 bit processing. They can however address 64 bits worth of data. And typically you don't do any processing on address registers in very many programs. So you are doing 32 bit math but have in excess of 4GB of ram that you can use. This is more relevant to systems that have a bunch of stuff running at once. While your game might only use 2gb of ram you could have windows and a bunch of other programs still using in excess of 2gb of ram without any major worry. Still using 4gb of ram is a task in itself.

Also with multithreading I don't see why everyone thinks it's that hard to implement. Any decent programmer should know how to do it fairly efficiently. The trick is to just do everything in batches. Also there is nothing wrong with threads accessing the same data at the same time. They just can't be changing that data. So if you had 32 integers and 4 threads doing nothing but summing them all up independently of eachother there would be no problems at all. Typically for multithreading you'd just have one main thread running and split to several when you came upon some data processing or numbers to be crunched.

Also with the numbers of threads being used in games those numbers can be somewhat deceiving. Typically you'd have 1 thread for each seperate network connection that existed. As well as other threads that typically do nothing more than sit there and wait for something to happen.
 
Anarchist4000 said:
Ok gonna clear a few things up here. Multithreaded would be much faster, given more than one core for processing. 64bit would just make things larger, more accurate. A 64 bit CPU will do almost nothing for the performance in games.

I might be wrong but my understanding of the x86-64 CPUs was that they do nothing but 32 bit processing. They can however address 64 bits worth of data. And typically you don't do any processing on address registers in very many programs. So you are doing 32 bit math but have in excess of 4GB of ram that you can use. This is more relevant to systems that have a bunch of stuff running at once. While your game might only use 2gb of ram you could have windows and a bunch of other programs still using in excess of 2gb of ram without any major worry. Still using 4gb of ram is a task in itself.

Also with multithreading I don't see why everyone thinks it's that hard to implement. Any decent programmer should know how to do it fairly efficiently. The trick is to just do everything in batches. Also there is nothing wrong with threads accessing the same data at the same time. They just can't be changing that data. So if you had 32 integers and 4 threads doing nothing but summing them all up independently of eachother there would be no problems at all. Typically for multithreading you'd just have one main thread running and split to several when you came upon some data processing or numbers to be crunched.

Also with the numbers of threads being used in games those numbers can be somewhat deceiving. Typically you'd have 1 thread for each seperate network connection that existed. As well as other threads that typically do nothing more than sit there and wait for something to happen.

well your kinda right
but to adress that much ram you need to be able to hold that adress in a reg
so you NEED a 64bit long (or longer Reg)

if you look up the X86-64 whitepaper you will that it does extend out the registers to 64bits past the 32bit EAX set
basicly AMD was what Intel did back with the 386 over the 286
when we went to 32bit extend the registers and add a mode

the AMD64 and i would asume EM64T have 4 working modes

Real mode: were it acts like very fast 286 this the mode you boot in till a OS loads
Protected mode: were windows normaly runs

now the new ones
compatably mode: this mode lets the CPU run both 32 and 64bit code but not 16 or 8 bit
and works for 32bit code like protected mode does for 16bit code
64bit mode: in this mode were most *nix OSs run is full 64bit no 32bit code can be run

with 32bit adressing you cant get over 3GB i think it is past that to 4GB you have to use PAE which is extends the adressing out to 36bits
http://en.wikipedia.org/wiki/Physical_Address_Extension

http://en.wikipedia.org/wiki/AMD64
if you look you can see the chart with the CPU modes
 
If there is no performance increase from 64bit other than memory, then theoretically a 16bit cpu would be adequate as well in a low memory app with a high enough clockspeed?
 
16 bit would be just as fast but on top of not being able to address much ram you'd have extremely shitty precision if you were doing any math.
 
Anarchist4000 said:
Also with multithreading I don't see why everyone thinks it's that hard to implement. Any decent programmer should know how to do it fairly efficiently. The trick is to just do everything in batches. Also there is nothing wrong with threads accessing the same data at the same time. They just can't be changing that data. So if you had 32 integers and 4 threads doing nothing but summing them all up independently of eachother there would be no problems at all.

You are oversimplifying here. There are many issues that needs to be dealt with. Many programmers have an idea what is required of multithreaded programming. But only a few can implement it effectively. There is no "trick" in multi-threading programming. What is important is coming up with architectures that promotes concurrent processing and designs that effectively deals with sychronization of data access and tasks.
 
Anarchist4000 said:
Also with multithreading I don't see why everyone thinks it's that hard to implement. Any decent programmer should know how to do it fairly efficiently.

given sufficient time, yes.
How many games have you heard of that were so far ahead of scheduel they were just sitting around the last few weeks hoping beta testers found bugs?
Multithreading add subsantial complexity to a project, not just in design but in debugging and patching.

The trick is to just do everything in batches. Also there is nothing wrong with threads accessing the same data at the same time. They just can't be changing that data. So if you had 32 integers and 4 threads doing nothing but summing them all up independently of eachother there would be no problems at all.

XBit Lab's and dual cores sharing data.

Even for non-modified data it takes Athlon64 and Penitum D 50-250 clock cycle delay to obtain data from the other core's cache. Only chips with a shared L2 right now can share un-modified data between cores in a timely mannor.
In most cases, your example would be an order of magnitude or two slower than just doing the work in a single thread.

Typically for multithreading you'd just have one main thread running and split to several when you came upon some data processing or numbers to be crunched.

using a few pre-existing threads in a divide by conqure role is possible. But the situation must warrant it.
 
Back
Top