# 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 6
# self = https://watcher.sour.is/conv/brixhka
@lyse Indeed I’m so glad to have gotten to the bottom of it 🤣
@lyse Indeed I’m so glad to have gotten to the bottom of it 🤣
@prologic but, did we? If the cache is 44MB, there has to be a way to allocate CACHE_SIZE + 5% of size (for grow, or overhead), up to TOTAL_RAM - 2% instead of trying to allocate memory that doesn’t exist. It seems, and feels, wrong.
The percentages above come from under my sleeve, but you get the gist.
@fastidious Yeah, we know what's happening, but not why the fuck it is this inefficient.
In order to understand that we’d have to go read the standard library source code on the Gob encoder and see wtf it’s doing with memory allocations
In order to understand that we’d have to go read the standard library source code on the Gob encoder and see wtf it’s doing with memory allocations