|
Josh @ Dreamland
|
|
Reply #31 Posted on: September 17, 2009, 02:58:41 pm |
|
|
Prince of all Goldfish
Location: Pittsburgh, PA, USA Joined: Feb 2008
Posts: 2950
|
I can see threading a pathfinding script, as long as you didn't constantly need the entire path. If it was optimized for threading, especially. Optimized in the sense that it can put multiple pieces together, including fixing the beginning and end of the path where the points may have moved during processing.
With things like threading, you'll lose the general-purpose functionality you get from simpler scripting, but ideally with a great speed gain.
|
|
|
Logged
|
"That is the single most cryptic piece of code I have ever seen." -Master PobbleWobble "I disapprove of what you say, but I will defend to the death your right to say it." -Evelyn Beatrice Hall, Friends of Voltaire
|
|
|
|
RetroX
|
|
Reply #33 Posted on: September 17, 2009, 05:22:54 pm |
|
|
Master of all things Linux
Location: US Joined: Apr 2008
Posts: 1055
|
Wow, why did I read that as CPU. :/
Anyways, threads are useful. For doing multiple things at once. Windows uses a thread for each application. A single thread for the OS is not one thread; it is many. It would make sense to use threads to run things in threads for speed, wait for all threads to finish, whereas if the threads do not finish within x time, it's considered too much lag and an error pops up. All of this is controlled from a separate thread.
why did everyone ninja me
doesn't SMF have an anti-ninja feature
oh, paged, stupid
|
|
|
Logged
|
My Box: Phenom II 3.4GHz X4 | ASUS ATI RadeonHD 5770, 1GB GDDR5 RAM | 1x4GB DDR3 SRAM | Arch Linux, x86_64 (Cube) / Windows 7 x64 (Blob)Why do all the pro-Microsoft people have troll avatars?
|
|
|
|
|
|
|
|
RetroX
|
|
Reply #39 Posted on: September 18, 2009, 02:33:54 pm |
|
|
Master of all things Linux
Location: US Joined: Apr 2008
Posts: 1055
|
Thing is, you need the application to do the splitting. Windows won't and shouldn't split the threads itself; that way, a game can split to one core and all applications can split to one, etc. For example, you should assign each core a name and task - for example, one is a "game" core, one is a "utility" core, etc. The OS should decide which core the thread should go to depending on the cores' activity, the requested core, and the resources required by the thread, merging and freeing certain cores according to required tasks, so the most is always used out of the cores. Obviously, that isn't happening right now.
|
|
|
Logged
|
My Box: Phenom II 3.4GHz X4 | ASUS ATI RadeonHD 5770, 1GB GDDR5 RAM | 1x4GB DDR3 SRAM | Arch Linux, x86_64 (Cube) / Windows 7 x64 (Blob)Why do all the pro-Microsoft people have troll avatars?
|
|
|
|
|
|
|
|
|