# 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 7
# self = https://watcher.sour.is/conv/rb7wmlq
And 32kb of RAM might seem like absolutely nothing, but y'know I kind of miss when developers had to be memory constrained, as odd as that might sound to say. Nowadays devs can put any amount of layers and bloat into software because "memory is cheap" and they just don't care.
The thing is... Memory isn't actually cheap. When you consider that most applications are in some way or another "Memory bound" and that Memory is the only resource that isn't compressible, this means you end up wasting other resources like CPU. This is one of the driving factors in my deciding to take on a new services, iif it is well written and consumes reasonable resources for what it does, or write my own. Things written in Java™ are _basically_ out of the question.
The thing is... Memory isn't actually cheap. When you consider that most applications are in some way or another "Memory bound" and that Memory is the only resource that isn't compressible, this means you end up wasting other resources like CPU. This is one of the driving factors in my deciding to take on a new services, iif it is well written and consumes reasonable resources for what it does, or write my own. Things written in Java™ are _basically_ out of the question.
This is _probably_ best visualized be real examples from my own infrastructure:
My infra consists of a 3x node Proxmox VE cluster (running Intel Xeon 1RU servers each with 32GB of memory). So you can see even though I pick and choose _quite deliberatly_ what I run, I'm still running out of memory.
This is _probably_ best visualized be real examples from my own infrastructure:
My infra consists of a 3x node Proxmox VE cluster (running Intel Xeon 1RU servers each with 32GB of memory). So you can see even though I pick and choose _quite deliberatly_ what I run, I'm still running out of memory.
This is _probably_ best visualized be real examples from my own infrastructure:\n\n \n\n \n\nMy infra consists of a 3x node Proxmox VE cluster (running Intel Xeon 1RU servers each with 32GB of memory). So you can see even though I pick and choose _quite deliberatly_ what I run, I'm still running out of memory.