garbage collection has to be done, if you don't free after you malloc in C/C++ you can blow up and end up with an OOM panic and be force killed by the kernel
coroutine scheduling only runs a background process when you are running on more than one kernel thread because it tries to parallelise as much as possible
this is one of the other deficiencies of go - if you need to do bulk compute it's better to refactor your processing unit as an independent process and coordinate them with an IPC, i have also done this, the difference is about 20% for compute bound heavy processing (it was a crypto miner) - vanity mining addresses, also, another example of what benefits in Go from this, whereas in languages with explicit access to kernel thread control can do this natively
mleku / mleku ✝Ⓐ☯︎
npub1fj…mleku
2024-02-08 04:01:15
in reply to nevent1q…u98p
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2024-02-08 04:01:15Event JSON
{
"id": "1827606390461794326c1c252c73d9384470f069b5bdcd0fb6d5d63253331ec7",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1707364875,
"kind": 1,
"tags": [
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"wss://relay.mleku.online/",
"Will"
],
[
"p",
"17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4",
"wss://relay.mleku.online/",
"elsat’s username"
],
[
"p",
"8fb140b4e8ddef97ce4b821d247278a1a4353362623f64021484b372f948000c",
"wss://relay.mleku.online/",
"The Fishcake 🐶🐾🐟🎂🇯🇵🥧"
],
[
"p",
"88a2c3b420b4a027706a98600d1fd744ac6cfd12e201b74189be5ef4b2b3aa45",
"wss://relay.mleku.online/",
"MF_HODL"
],
[
"e",
"39b34a65a5a1c2cf35ff2e3142df83c8002e651d33154ed98f2108691215cb92",
"",
"root"
],
[
"e",
"c89b9ceb8d988f09cad6e68b6c212ea69a5c379bb16f637d99f6a0a0a7f27fef",
"",
"mention"
],
[
"e",
"6ec75f4d0f0d7d1df05d46745586ef39c609dffbc3a00a02e65c972f183f9c47",
"wss://nostr.mutinywallet.com/",
"reply"
],
[
"client",
"Coracle",
"31990:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:1685968093690"
]
],
"content": "garbage collection has to be done, if you don't free after you malloc in C/C++ you can blow up and end up with an OOM panic and be force killed by the kernel\n\ncoroutine scheduling only runs a background process when you are running on more than one kernel thread because it tries to parallelise as much as possible\n\nthis is one of the other deficiencies of go - if you need to do bulk compute it's better to refactor your processing unit as an independent process and coordinate them with an IPC, i have also done this, the difference is about 20% for compute bound heavy processing (it was a crypto miner) - vanity mining addresses, also, another example of what benefits in Go from this, whereas in languages with explicit access to kernel thread control can do this natively",
"sig": "d936705337818baaf55a77e1a25eb01a0785545d9e429d5d6f02b4f8e4bb00ab5f6d2101809d26daeafc8ba794ee366a9c5ab876571f98c1ca970517e522065e"
}