# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 9
# self = https://watcher.sour.is/conv/vro2qgq
Can I ask a potentially dumb question? Does Docker use oodles more resources than running a native instance of an application? I've never used it and thought it made good use of virtualisation and would have a bit of overhead, but then I've seen tests that say it's not far off native in most aspects... so I dunno.
@eldersnake I should add the reason for my confusion is I've seen VPS providers recommend higher system requirements when selecting a Docker instance.
@eldersnake No not _really_. There is a little overhead as with any layer of abstraction, but it's not that bad. I can measure it on some of my clusters if you like and give you real figures.
@eldersnake No not _really_. There is a little overhead as with any layer of abstraction, but it's not that bad. I can measure it on some of my clusters if you like and give you real figures.
@eldersnake If you want lightweight containers you should look into something like unshare (_part of the bustbox userland_) or box -- If you're after a very lightweight Linux OS that supports Docker fully (_including Swarm_) you should look into µLinux
@eldersnake If you want lightweight containers you should look into something like unshare (_part of the bustbox userland_) or box -- If you're after a very lightweight Linux OS that supports Docker fully (_including Swarm_) you should look into µLinux
@prologic Awesome thanks, just when you're not busy figures would be interesting :) Even if there was only minimal overhead, I was, for example, always going to use yarnd natively on my Raspberry Pi because I'm happy to squeeze out all the resource saving I can, but I was just curious.
@eldersnake The reality is that most of the "things" I write, I write in Go and I _normally_ err on the side of portability, that means I tend not to use anything that requires any system libraries / CGO. i.e: static linking. So the binaries are fairly portable. The only exception to this has been yarnd itself which _does_ link against some ffmpeg libraries and webp libraries and image and video processing.
@eldersnake The reality is that most of the "things" I write, I write in Go and I _normally_ err on the side of portability, that means I tend not to use anything that requires any system libraries / CGO. i.e: static linking. So the binaries are fairly portable. The only exception to this has been yarnd itself which _does_ link against some ffmpeg libraries and webp libraries and image and video processing.