verita84 :Debian_logo: :firefox: :bing: :android: (npub1zna…wtpl) npub1kpwlxpzkxfmuxjmzc2wp3rf9vjg0sgydmlhsnrgqr3maf59h86qqdxxzz4 (npub1kpw…xzz4) the enterprise people are where i read about monstrously sized stacks and heaps with nontrivial processing times.
you can route around some of it at the mq layer, like telling rabbit to only dispense one message per acknowledgement. then when the app server inevitably takes its shit, only two requests in flight are stalled. or one job, in a pull system.
you get stuff like shenandoah which is a very complex collector. but you won't get an interrupt "GC IS ABOUT TO HAPPEN! PANIC!" or an option to pre-emptively warn the system. there is typically a command to attempt a collection right now, but its not probative. if the gc was doing to do it it takes that as an invitation to do it now, rather than let you prep for it.
afaik enterprise code just invests in more gcs that strive to be better at being invisible, rather than cooperative ones.
Q.U.I.N.N. /
npub1f8…vzu5u
2023-08-23 23:43:05
in reply to nevent1q…jmcr
Author Public Key
npub1f8e6w3kg6cptk4ljl09ua3vezr7gws4jcuwyvzdnpytsnlp2yd6savzu5uPublished at
2023-08-23 23:43:05Event JSON
{
"id": "1204eabc01f957ab281bf9412a9a597f8534c6e38f2ac1b71e8a83e37f73b905",
"pubkey": "49f3a746c8d602bb57f2fbcbcec59910fc8742b2c71c4609b3091709fc2a2375",
"created_at": 1692834185,
"kind": 1,
"tags": [
[
"p",
"14fac33f299949ee9572e1b41c5e4de0f6e564f5499c64ff7de703213e94399f",
"wss://relay.mostr.pub"
],
[
"p",
"b05df304563277c34b62c29c188d256490f8208ddfef098d001c77d4d0b73e80",
"wss://relay.mostr.pub"
],
[
"p",
"12da98a3a66fb47b43526b1b241e91df632bfd4058dc5364938dc932fe931118",
"wss://relay.mostr.pub"
],
[
"e",
"bf70da7a552b18248122fc8ce105baa98391a4152e0b4e7cb80b074c0fd2f846",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://blob.cat/objects/a50140ad-33a0-4edf-b933-698e0741b1b2",
"activitypub"
]
],
"content": "nostr:npub1znavx0efn9y7a9tjux6pchjdurmw2e84fxwxflmauupjz0558x0sqmwtpl nostr:npub1kpwlxpzkxfmuxjmzc2wp3rf9vjg0sgydmlhsnrgqr3maf59h86qqdxxzz4 the enterprise people are where i read about monstrously sized stacks and heaps with nontrivial processing times.\n\nyou can route around some of it at the mq layer, like telling rabbit to only dispense one message per acknowledgement. then when the app server inevitably takes its shit, only two requests in flight are stalled. or one job, in a pull system.\n\nyou get stuff like shenandoah which is a very complex collector. but you won't get an interrupt \"GC IS ABOUT TO HAPPEN! PANIC!\" or an option to pre-emptively warn the system. there is typically a command to attempt a collection right now, but its not probative. if the gc was doing to do it it takes that as an invitation to do it now, rather than let you prep for it.\n\nafaik enterprise code just invests in more gcs that strive to be better at being invisible, rather than cooperative ones.",
"sig": "b6a37efa22fd982097c07afa6793ebc2e589fdec728142c149149a4bebe2bbae87606ad9076840fd5357e8a77d21dd73a6a4553fb151892e66e5ae14a8a3b53e"
}