hannes changed the topic of #mirage to: https://mirage.io - https://github.com/mirage/mirage-www/wiki/Call-Agenda - this channel is logged at http://irclog.whitequark.org/mirage/ - MirageOS 3.5.0 is released - happy hacking!
pie_ has quit [Remote host closed the connection]
pie_ has joined #mirage
Haudegen has joined #mirage
pie_ has quit [Ping timeout: 258 seconds]
mort___ has joined #mirage
mort___1 has joined #mirage
mort___ has quit [Read error: Connection reset by peer]
pie_ has joined #mirage
pie___ has joined #mirage
pie_ has quit [Ping timeout: 244 seconds]
Haudegen has quit [Read error: Connection reset by peer]
mort___1 has quit [Quit: Leaving.]
<apache2> ehirdoy1: you mean statically? I don't think so.
Guest11648 has joined #mirage
ansiwen_ is now known as ansiwen
pie_ has joined #mirage
pie___ has quit [Ping timeout: 276 seconds]
Guest11648 has quit [Remote host closed the connection]
Haudegen has joined #mirage
pie_ has quit [Remote host closed the connection]
pie___ has joined #mirage
pie___ has quit [Remote host closed the connection]
pie___ has joined #mirage
mort___ has joined #mirage
mort___ has quit [Client Quit]
mort___ has joined #mirage
mort___ has quit [Read error: Connection reset by peer]
mort___ has joined #mirage
mort___ has quit [Client Quit]
mort___ has joined #mirage
mort___ has quit [Client Quit]
mort___ has joined #mirage
pie_ has joined #mirage
pie___ has quit [Ping timeout: 250 seconds]
<ehirdoy1> apache2: any way to get memory usage at runtime?
<apache2> yeah
<apache2> there's a bunch of stuff in the Gc module that you can use to pull information like that
<apache2> ehirdoy1: Gc.( (stat()).heap_words) maybe
<apache2> I don't know what this number represents, so you would have to look that up, but I think you can get a number like that. On top of that number is the size of whatever mappings your unikernel gets loaded with in memory (like the code and static data)
<apache2> you could probably look at the ELF binary with the `readelf` command, but it might be easier to inspect the binary while it's running in its native environment -- which backend are you targeting?
<apache2> and easier way again might also be to just do binary search, launching it a few times with various amounts of memory allocated and seeing when it stops crashing under casual load.
mort___ has quit [Ping timeout: 264 seconds]
Haudegen has quit [Read error: Connection reset by peer]
pie___ has joined #mirage
pie_ has quit [Ping timeout: 245 seconds]
pie___ has quit [Ping timeout: 258 seconds]
Haudegen has joined #mirage
Haudegen has quit [Remote host closed the connection]
pie_ has joined #mirage
Haudegen has joined #mirage
Haudegen has quit [Remote host closed the connection]