There's more than one way to do things | |
PerlMonks |
Re^7: Standard way to convert timezone in multithreaded scriptby zentara (Archbishop) |
on Nov 25, 2009 at 10:23 UTC ( [id://809308]=note: print w/replies, xml ) | Need Help?? |
... yeah soory BrowserUk... i concede that you have every right to jump on my case for what i said.... sorry if i spewed some ignorance about the functioning of multi-core motherboards, but i don't have one ...i do wonder about the wisdom of allowing a process to launch threads into other cores, other than the one it's parent exists in..... i'm in that zen trap, where the external world becomes a reflection of the inner mind, and i use this as a guide to developing my artificial intelligence strategy. ..... and in my inner mind, i have distinct barriers between cores ( so to speak)...... my visual cortex dosn't allow the audio core processing to occur in the visual core... etc.... a separation for safety.... and in that train of thought, i require that i can reset a single core, without resetting the whole set of cores...... if my collision-detection system goes bonkers, i don't want it to affect my steering...etc. .... and i don't want to have to deal with worrying that maybe the collision-detection code somehow got it's malfunctioning code into my steering core .... but i guess for gamers, or pure dedicated number crunching, this cross-core core chaos would allow more speed.... but at a risk
.... another point that seems troublesome, is that can you be sure that the thread spawned will go into another core?.... for instance.... to use tirwhan's 1-liner as an example..... he says as you spawn muliple threads, they automatically get assigned to other cores..... but what if one core is already heavily loaded?..... wouldn't the scheduler tend to drop more than one thread into one of the unloaded cores?....... or is there a way to specifically direct which core the code block goes into?..... otherwise 8 threads could end up like 1 in cpu0, 3 in cpu1 , and 4 in cpu2 because cpu5 thru 7 are already running a heavy load .... anyways..... it seems like all this multicore cross-core-exection stuff is aimed at gamers, and a security grade processor would automatically deny this behavior to confine all bad-acting apps and their spawn( whether it be forks or threads) to the originating core ....but maybe i'm just an old dog, whose is more worried that someone is going to steal my bone, than moving my bones around faster ...... fwiw... my spaceship controls have core separation :-)
In Section
Seekers of Perl Wisdom
|
|