<iced-quinn/> on Nostr: verita84 :Debian_logo: :firefox: :bing: :android: npub1kpwlx…xxzz4 the enterprise ...
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.
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.