single machine - Page 265

RoboForm Steps Up Into Enterprise Security

RoboForm Enterprise provides a simple alternative to enterprise single sign-on systems that achieves many of the same benefits at a far lower cost.

Why C++ people loves multithreading when it comes to performances?

I have a question, it's about why programmers seems to love concurrency and multi-threaded programs in general. I'm considering 2 main approach here: an async approach basically based on signals, or just an async approach as called by many papers and languages like the new C# 5.0 for example, and a "companion thread" that maanges the policy of your pipeline a concurrent approach or multi-threading approach I will just say that I'm thinking about the hardware here and the worst case scenario, and I have tested this 2 paradigms myself, the async paradigm is a winner at the point that I don't get why people 90% of the time talk about concurrency when they wont to speed up things or make a good use of their resources. I have tested multi-threaded programs and async program on an old machine with an Intel quad-core that doesn't offer a memory controller inside the CPU, the memory is managed entirely by the motherboard, well in this case performances are horrible with a multi-threaded application, even a relatively low number of threads like 3-4-5 can be a problem, the application is unresponsive and is just slow and unpleasant. A good async approach is, on the other hand, probably not faster but it's not worst either, my application just waits for the result and doesn't hangs, it's responsive and there is a much better scaling going on. I have also discovered that a context change in the threading world it's not that cheap in real world scenario, it's infact quite expensive especially when you have more than 2 threads that need to cycle and swap among each other to be computed. On modern CPUs the situation it's not really that different, the memory controller it's integrated but my point is that an x86 CPUs is basically a serial machine and the memory controller works the same way as with the old machine with an external memory controller on the motherboard. The context switch is still a relevant cost in my application and the fact that the memory controller it's integrated or that the newer CPU have more than 2 core it's not bargain for me. For what i have experienced the concurrent approach is good in theory but not that good in practice, with the memory model imposed by the hardware, it's hard to make a good use of this paradigm, also it introduces a lot of issues ranging from the use of my data structures to the join of multiple threads. Also both paradigms do not offer any security abut when the task or the job will be done in a certain point in time, making them really similar from a functional point of view. According to the X86 memory model, why the majority of people suggest to use concurrency with C++ and not just an async aproach ? Also why not considering the worst case scenario of a computer where the context switch is probably more expensive than the computation itself ?

Search Results

Search found 34186 results on 1368 pages for 'single machine'.

Page 265/1368 | < Previous Page | 261 262 263 264 265 266 267 268 269 270 271 272 | Next Page >

- by user1849534

- by JuP

- by Nick

- by Jason

- by rahi

- by M Legoh

- by db42

- by Fak365

- by Bitmap

- by daveu1

- by BT643

- by Gaurav_Java

- by darga33

- by Sankalp Kota

- by Crizly

- by MegaBrutal

- by manseuk

- by user1661479

- by luxifer

- by Jesi

< Previous Page | 261 262 263 264 265 266 267 268 269 270 271 272 | Next Page >