-
The advantage of multi-core over a single core is that it can really process multiple things at the same time, so if a program wants to get better performance on a multi-core CPU, multi-threading is necessary. However, the use of multi-threading involves the problem of data synchronization between threads, and programmers must coordinate the access and processing of data between programs. However, I don't think the difference between multi-core programming and single-core programming is that it is a matter of thread synchronization, because single-core programming can also use multi-threading, and it also needs to face the problem of thread synchronization.
The same ** can run well on both multi-core CPUs and single-core CPUs without special optimization, but the operating efficiency is different. So I think the difference between multi-core programming and single-core programming is the urgency of the need for multi-threading technology. If the program is programmed for a multi-core environment, then multi-threading technology must be used for better performance; If the program is only for a single-core environment, it is not so sensitive to multi-threading, but if it is multi-threaded, it can also get a performance boost once it is running in a multi-core environment.
-
Exclusive locks on resources. There are conflicts due to the limited resources and the unlimited number of programs running at the same time. It's about to solve the problem with "locks".
Single-process threads, not required.
Multi-process threads, required.
-
There is a difference in how multi-core programming is how to efficiently use the CPU to process transactions.
One is for the CPU and the other is for the thing itself.
-
As long as the architecture is the same, the main frequency is the same, and the cache is the same, there is no difference in the speed of a single process between a single core and a six-core process. Dealing with simple single tasks is a single core operation, but for example, games or professional software, multiple cores are often optimized, in fact, multiple cores work at the same time, that is to say, when playing mainstream games and other tasks, there is a difference between single core and multiple cores. Multitasking at the same time doesn't put any pressure on the hard drive, as long as the CPU is strong enough and the memory is large enough.
At present, the dual-core has become more and more low-end, and in the past, the mainstream high-end CPU was occupied by high-frequency dual-core such as E8400. In the previous generation, there was also the i5 600 series that occupied the high-end thousand-yuan market, in fact, the attention was very low, and the basic light was covered by the i5 700 series quad-core. At present, Intel no longer releases high-end dual-cores, SNB CPUs, the highest dual-cores are only i3 2100, AMD only has X2 560 and other large cache dual-cores, and soon the bulldozer will be released, and the dual-core will be more and more low-end.
-
You may confuse the concepts of task count with thread count, and the CPU can handle one thread with one core (one core with hyper-threading technology can handle two threads) rather than one task. We know that when any application is running, a process has multiple threads, taking QQ as an example, a QQ process has 20-30 threads: so ordinary dual-core or quad-core CPUs will reflect differences in the application.
And yours is only a single core, you can only process one thread per unit of time, of course, the efficiency can not be compared with multi-core, many software has been optimized for multi-core CPUs, and even newer operating systems (Win 7) natively support multi-cores, so it is necessary to have a multi-core CPU.
-
There is a difference,It depends on whether the software support is supported,If it is supported, the six cores can play their own performance well,Of course, it will be much faster than the dual core。 But nowadays the software is generally optimized for dual-core. So there's no need for more cores
-
Most of the current software has supported multi-core, as for whether to upgrade or not, depending on your own use, the computer can meet the requirements and will not be upgraded, and if you feel that the computer is not good, you will upgrade.
-
If the program is single-process, single-threaded, the processing speed of a multi-core CPU is theoretically the same as that of a single-core CPU.
-
There is still a difference, assuming that except for the number of cores, everything else is the same. They work in the same way that a single-cylinder car is running on the road as a six-cylinder car, and when we're all empty and only 20 yards, there's no difference. When we needed to run 100 yards, the single cylinder couldn't run.
Or when we need to run with a load, a single cylinder can't do it. So when you say this assumption, a big key depends on the requirements of the program you are running it in. But judging from the current software market, the dual-core processor can be used for office and movies.
-
This is like one person doing things and multiple people doing things, the more people do things, the more efficient they are, in detail, when a single-core CPU processes multiple processes, it must be processed one by one, and a multi-core CPU is to process multiple processes at the same time, and the speed is of course self-evident
-
In the case of hyper-threading technology, both single-core and multi-core CPUs process concurrent processes in parallel, but the number of single-core parallel processes is much lower than that of multi-core. Single-core is more likely to feign death in multi-process than multi-core.
Multi-core is not just a few more combinators, including the first and second level caches are also independent.
-
One person resists a pile of wood, and a group of people resists a pile of wood.
-
I guess you're referring to multicore programming.
Multi-core programming is a technology that programmers must understand nowadays, and unlike the original single-core technology, multi-core programming pays more attention to the architecture of the program, the distribution of tasks, and the load of each processor. The multi-core programming tool we use now is OpenMP for the shared storage mechanism, and the main shared memory protection mechanism is the distributed lock mechanism.
-
It depends on what you do! If you sit on the upper and middle floors, it doesn't matter at all!
If it's sitting in embedded development, it kind of touches.
-
1. When writing programs, you can improve the corresponding speed of the integrated development environment.
2. When compiling the program, the multi-core computer can shorten the compilation time.
-
Single-core and single-thread are processed one by one, and multi-core and multi-threaded are processed at the same time.
Bell programming is okay, but it is more recommended to choose Tongcheng Tongmei's children's programming course. Tongcheng Tongmei children's programming experience class, click to sign up for a free trial. >>>More
Similar to PASCAL language, but with pointers, and PLC programming that supports the IEC61131-3 standard.
**The Way of Microsoft Core Technology Series.
Executive summary. From the perspective of a Microsoft insider, this book reveals all aspects of software coding, software testing, and project management. >>>More
There are a lot of programming points, I don't know which programming you are referring to? >>>More
I think it's okay, now the system is mostly written in C, but it may be written in C at the beginning, and then the system is bigger, it is difficult to change it to C++, because the system is relatively large, so I think it is good to write in C++, easy to control, of course, the speed is to be discounted, but stability and flexibility should be more important, after all, the slow is better than the unmodifiable and the old crash, and the speed of C++ is not much worse than C, and even faster in some places, because now C++ development is much faster than CAs Bjarne Stroustrup said, learning C is just about dealing with the ** that is being taken as a legacy, hehe. I wonder if that's a bit too much? >>>More