hrgiger

I am recently studying hpc configs and the docs I follow most (amd,suse) recommends blocking thp by default which I was able to replicate performance impact myself as well, on the otherside standard hugepages brings lot of advantage, I do setup during kernel boot but didnt test properly, currently using 4GB. If you really wanna bypass page latency I recommend buying a cheap persistence memory, not all filesystems support yet , (ext4 and xfs ?) but with -o dax mount option you dont use pages, if data is temporary tmpfs with hugepages as far as I can see quite common usage but I also found kernel memblock argument by simulating non-existent persistent memory and mounting a filesystem with dax brings similar performance or even faster most of my cases yet still you wanna script each time boot mkfs/mount

There are plenty of resources on search engine results , what did you find in particular those books stays top of the others?

You might wanna validate your back propogation *or the final cost against a hand written very small network to see what went wrong

Can you add some details about what are the most complex components in your system? Also what parts you implemented from scratch? I see you still use torch

unconditional worldwide true peace (not brought by weapons)

Well quick google search tells me there is about 50 to 100 year fossil resources left, thats about a lifetime for a currently newborn or more optimistic next 2 generation

Certainly he is an exceptional programmer

I understand your point and you are completely right, but on their perspective your experience from multiple aspects of codebase is still valuable contribution and making a difference isnt it.

"showing porn to people against their consent is a form of sexual abuse" is more descriptive then your quotes I believe, at least this kind of precautions adds an alarm/notification options between kids in social media and twisted adults

so you are project manager?

you sleep i watch