Re:Show HN: Mmm – manual memory management for Go
by teh_cmc on Monday November 30, 2015 @02:07PM
(#10651059)
Yes, as I said in this comment [1]; my real issue here is lengthy GC pauses, which cause peaks in response times.
Regarding overall performances, I'm not really convinced that the reflect calls affect them that much (there's 2 reflect calls per Read() or Write() call), but I honestly just don't know, I'd have to bench to be sure.
Although, if it turns out to actually be an issue, you can still use Pointer() to keep references to your unmanaged heap and you'll be able to work with your data without GC nor reflection overhead.
Regarding overall performances, I'm not really convinced that the reflect calls affect them that much (there's 2 reflect calls per Read() or Write() call), but I honestly just don't know, I'd have to bench to be sure. Although, if it turns out to actually be an issue, you can still use Pointer() to keep references to your unmanaged heap and you'll be able to work with your data without GC nor reflection overhead.
[1] https://news.ycombinator.com/item?id=10650885