# 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 5
# self = https://watcher.sour.is/conv/r4ns5ha
@lyse I analyzed all of the goroutines in yarnd and they are all accounted for In summary:
- 1x GC
- 1x Server
- 4x TTL Caches
- 10x Workers + 1x Dispatcher
- 1x Cron scheduler
I'm not counting any of the profiler debugging goroutines, and there's also a few goroutines to do with networking. But pretty sure given what yarnd does the ~50 or so goroutines on startup is _actually_ normal. That being said though, perhaps there is room to condense this somewhat, but as goroutines are cheap 🤷♂️~
@lyse I analyzed all of the goroutines in yarnd and they are all accounted for In summary:
- 1x GC
- 1x Server
- 4x TTL Caches
- 10x Workers + 1x Dispatcher
- 1x Cron scheduler
I'm not counting any of the profiler debugging goroutines, and there's also a few goroutines to do with networking. But pretty sure given what yarnd does the ~50 or so goroutines on startup is _actually_ normal. That being said though, perhaps there is room to condense this somewhat, but as goroutines are cheap 🤷♂️~
@prologic Cool, thanks for the analysis! So you listed 18 goroutines, profiler goroutines will be hopefully not present in non-debug mode. That leaves about 30 for networking. Constant networking seems a bit odd, but okay. Yeah, we probably don't need to worry about getting them reduced. Just for the general understanding what's going on.