strongly-typed, variable-length pages. I'd like to guarantee that the app
won't take up move than X amount of memory, e.g. 3/4 of main memory. In a
system with generic pages of well-known lengths, this is super easy:
Allocate n buffers of size page_length, if no buffer is free use some
strategy (LRU, for instance) to find one to overwrite.
When your buffers are of variable length, this gets more complicated. When
your buffers are actually strongly typed (e.g. the buffer has
variable-length fields), that makes it more complicated. And then when your
language has GC, it seems to me it'd be even *more* complicated--you can't
explicitly deallocate and/or don't have a lot of control over how you use
Has anyone worked on anything in golang like this? It's totally possible
I'm just thinking about the problem the wrong way, too. Anyone have
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.