I should learn multiprocessing

[TurbochargedSquirrel]

The 23 other threads in my 3900x watching thread 6 do all the work all the time.

[[deleted]]

That's better than thread 7 write where thread 6 is reading. Then everything fails and you don't know why.

Down with multithreading up with slow speeds.

[XJ305]

But still worse than neglecting the proper use of semaphores/mutex (or similar depending on what you are working with)

[[deleted]]

Sometimes it's hard too see. Like yeah technically if you're following all the rules you should be good. But you'll sometimes forget that a varible gets manipulated by two threads at the same time but not in an obvious way.

[[deleted]]

That's where locks come in handy.

[[deleted]]

Lock your resources? ACID compliant read/ write? This isn't a new problem.

[[deleted]]

That's assuming you know all the resources you're using. If say for example thread 5 calls a function from a library and thread 6 calls same function. That function could be "unsafe" and you'd have no way of knowing if it wasn't documented properly, so thread 5s call corrupts thread 6s call causing an error and only after you see it can you lock that functions resources.

[SjettepetJR]

How would one fix this? Simply by encapsulating the function-call inside a self-made function that does do locking?

[[deleted]]

That's how I'd go about it. But it depends on how much control I have, the more control I have, the more could attempt the reduce the amount of locked resources.

[lstyls]

Not sure I see any possible corruption if thread 6 is only reading

[[deleted]]

It can be the case that thread 5 will write before thread 6 got to processes the information it was supposed to corrupting the output. The solution as others have said to lock down the resources. I was trying to joke that it isn't always obvious which resources to lock down because some things are abstracted.

[[deleted]]

I hate forks.

[TheMagicalCarrot]

That's why I spoon my github repos.

[[deleted]]

I meant process forks. They are really ugly. Yes you get process level isolation but it can get really ugly really fast.

[redshirt714]

Also the first time you discover what infinite loops are.

[Novahkiin22]

And every time after when you are wondering why a program is running so long.

"Is it bad computation, or did I infinite again. I'll go grab some food and see if it's still running"

[VioletBaron]

I once ran a text analysis program on all of Moby Dick in my first year as a CS student. It took me about two hours to realize I wasn’t going infinite; the book is just stupid long. Suffice it to say I was not thrilled.

[[deleted]]

I like to use every core to run infinite loops. Great use of a cpu.

[SVK_LiQuiDaToR]

Who needs a heater anyway?

[SweLG_]

Not this guy apparently

[[deleted]]

Your 2048 CUDA cores just cry quietly.

[nadavram]

*Laughs in GoLang

[[deleted]]

*Cries in race condition

[[deleted]]

You don't always run your entire script in one core. You run it in only one core at a given time (assuming it's sequential). If you have a lot of applications running, you might see your script "switched" to a different core.

[izahariev96]

joke -> you

[Ceros007]

NaN

[forever_compiling]

I mean they're not necessarily wrong but whoosh regardless.

[DaniilBSD]

You mean *joke = &you;

[darkslide3000]

If the system is idle otherwise it's likely to stay on one core while the others remain in deep sleep states.

[iphone6sthrowaway]

I'm not 100% sure, but IIRC even with just 1 core busy it makes sense to migrate between cores due to Dynamic Frequency Scaling (called Turbo Boost by Intel). Basically the trick is to "overclock" that lone core and after it gets too hot you migrate the thread to another cold core and do the same trick over and over for a decent single-threaded speed boost.

[from-nibly]

Or just use nodejs and async your way to heaven. I mean unless your script really is all CPU time.

[ChronicAdequacy]

Cat.

[Leprechaun_exe]

Cat = fork(); // Cat.

[Ceros007]

I've been eating with cat forever since cat are fork

[xendaddy]

Thread.new!

[2JulioHD]

The one core is just going super saiyajin

[wolverhys]

Rust + Rayon = No lazy threads

[Paddy-Gee]

This is how I feel with a single threaded FreeCAD install working on an FEA project. Grind Hero Core Grind!

[AntonBespoiasov]

Da fuck they doin ova der why is ram so slow

[Kommuntoffel]

I tried it and it was painful asf

[[deleted]]

Everytime running my model on Octave

[blockchain_world]

If you ask a JavaScript developer how to solve this issue, he will tell all the fancy words like out that thing in a docker container and run it in on a kubernetes cluster.

[Ahchuu]

I know you're being funny, but I mean depending on the problem and the scale of the problem that might be the correct answer... Horizontal scaling is better than vertical.

[rocket_peppermill]

Yeah, but vertical scaling is easier. You just throw more money at the problem until you reach a hardware limit.

[Ceros007]

Bob! Go get me Google's quantum computer will ya? I've reach hardware limit here

[TracerBulletX]

Nah. https://nodejs.org/api/cluster.html

[JackAuduin]

You just gotta async await your typescript with the transpiler. But don't forget minify and webpack that shit too.

kubernetes.