4 ms·
I don't write OS kernels, I write rails application. I don't give a rat's ass about the OS kernel then stop spouting off uninformed comments about how processe
by crabapple 18y ago
I don't write OS kernels, I write rails application. I don't give a rat's ass about the OS kernel
then stop spouting off uninformed comments about how processes are scheduled
The Rails applications themselves don't need to be altered to run in a multi-core environment.
nor do any other program compiled for that architecture. its the OS that schedules processes, not your userland program. the point is, some programs can be written in a way that makes it easier for the OS to exploit multicore. since ruby is not a functional language, my guess is that it would tend to not help the kernel exploit these resources. but obviously in the worst case, a process can run inside one core and never get the advantages of the rest of the chip architecture. this is about exploiting multicore
Got it?
yes, i get that you know very little about how computers function
- swombat 18y agonor do any other program compiled for that architecture Then none of the people writing those programs need to know or care about parallelism. Therefore, the core message of the article is brain-dead.
- crabapple 18y agoNO. why don't you READ before you reply a program compiled for a multicore CPU will RUN. the question is how OPTIMALLY does it run. a program with no potential for parallelism will not get any parallelism. it will run, but run slow compared to programs designed for parallelism. programs written to exploit parallelism will be programs that bring new approaches to data and state. functional languages provide this today, which is why lots of people think they will be the way forward for multicore. honestly i think you are just bordering on being a troll. why don't you do some reading on this topic before writing more uninformed replies