Show newer

@jojo

Is that supposed to be a threat, he is like the court jester, just runs around making a fool of himself. Mostly just good entertainment at this point.

@11112011 @ethot @Nukie

@pganssle ok just making sure :) thanks. going to give this solution a try.

@pganssle by the way I notice you used threading.RLock in your example.. will that even work, I figured I needed to use multithreading.RLock

@Pat You now have a 20 gig quota and bypass the auto-blacklist.. should you max out the quota just let me know and as long as yoru videos aren't against our ToS I'll be happy to increase it as needed.

@pganssle Excellent selection, yea that might be what id go with.. should be the best way to keep contention as minimal as possible for the number of locks used, Thanks.. Plus that has the advantage of scaling to arrays of enourmous size, which is a possiblitility as I could see 3900 x100 array as being a perfectly reasonable max (that would represent only 2 weeks of stock data during RTH, less otherwise).

@bonifartius We would say "He has just enough knowledge to be dangerous." I wouldn't be surprised if it comes from the germans.

Always cracks me up how all our sentance-long phrases boil down to a word or two in german :)

@pganssle massive parallelism is a lot of fun in any language, even in python with all its annoyances its still a fun task.. seen my CPUs all light up to 100% (I have 32 CPU cores) and my run time go from 2 hours to a minute or two is very pleasurable

@pganssle well there are only 32 processes, the locks are as many as they are however because of how i access a rather large array that all the processes share and write to.. In short the array needs a element-level lock (mostly because each element acts as a counter where += operations need to be atomic), but there is never a need for any one process to lock more than one cell at a time.

So i created an array of locks that is as big as the array itself in an attempt to minimize thread contention.

Works great at minimizing thread contention, it runs almost as fast as the locks not being there (with no lucks there was minor corruption for obvious reasons).. but that memory issue.

So yea not an issue with running tons of processes, i just need tons of Rlocks

@bonifartius yes magnetic field decay exponentially.. no it wont require exponential power.

The energy put into a magnetic field is recovered each cycle, presuming of course you design the device to not radiate into the far-field (which isnt really going to happen at the frequencies these things operate at the size of the pads).

so while you do need more instantaneous current/voltage to produce a bigger field, that is almost fully recovered and doesnt actually cost you anything.

Basically in technical terms when it isnt charging something it costs you now "real power" but exhibits what we call "apparent power"

@pganssle I would agree with that.. my criticism isnt so much that python doesnt scale.. its more that the framework isnt the nicest for getting it to the point that it can.

@pganssle though I will say one thing has been infuriating me that i cant figure out whats going on and there is nothing on google... apparently if i create more than about 500 multiprocessing RLocks I get an out of memory error (and we are talking a 64 gig system). I am on docker and I am pretty sure its actually related to the shm size which when upped from 64 M to 2 gig was able to handle the 500 RLock (before i couldnt even get taht much).. but im not sure as it doesnt appear to actually **fill** the shm by nearly that much (though it does fill it a few 100M now)...

Very weird problem but eh, for now im just limiting my algorithms lookback to 500 minutes and it works.

Other than that i figured out most of the multiprocessing problems and have what used to take 2 hours to run down to a minute.

@StephenBeers I leave the door wide open when i use the bathroom in restaurants.

@admin

I suspect previews get queued and are probably rate limited from YT's end. So likely that is the case.

@FailForward

@FailForward It could be that its just a limitation of QOTO or a bug with the version. If you happen to add this as a ticket on our git I can investigate it at our next upgrade, which hopefully is in the fairly near future.

Show older
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.