# 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 28
# self = https://watcher.sour.is/conv/6bi4vaq
Noticing a fairly slow posting time. Well, posting a reply is taking longer than I remember. I wonder if it is the same whilst posting a new twt.
Yes, it is slow whilst posting a new twt. Maybe because of my pod’s huge cache?
@fastidious Not seeing any lag in posting here... πŸ€”
@fastidious Not seeing any lag in posting here... πŸ€”
@fastidious How slow are we talking? Can you measure it?
@fastidious How slow are we talking? Can you measure it?
Nevermind I can see it on your pod:


# HELP yarnd_cache_last_processed_seconds Number of seconds for a feed cache cycle
# TYPE yarnd_cache_last_processed_seconds gauge
yarnd_cache_last_processed_seconds 13


Hmmm looking at the code, I _think_ there's a missing "async" call there. One moment...
Nevermind I can see it on your pod:


# HELP yarnd_cache_last_processed_seconds Number of seconds for a feed cache cycle
# TYPE yarnd_cache_last_processed_seconds gauge
yarnd_cache_last_processed_seconds 13


Hmmm looking at the code, I _think_ there's a missing "async" call there. One moment...
The problem is... If I make this "async", you will not see your own new post immediately as you do now (_well it's quite quick for me πŸ˜…_); instead it will only appear some time later after a few refreshes 😒 Hmmm πŸ€”

Do we need to optimize how your own feed is updated and rather then refreshing the entire cache (_expensive_) figure out a way to update a subset that your new post affects?_
The problem is... If I make this "async", you will not see your own new post immediately as you do now (_well it's quite quick for me πŸ˜…_); instead it will only appear some time later after a few refreshes 😒 Hmmm πŸ€”

Do we need to optimize how your own feed is updated and rather then refreshing the entire cache (_expensive_) figure out a way to update a subset that your new post affects?_
@prologic yes. πŸ˜‚
@fastidious Will you be around / active on IRC or Video conf to test a fix? πŸ€”
@fastidious Will you be around / active on IRC or Video conf to test a fix? πŸ€”
@prologic tomorrow, for sure, yes. I am in bed now, waaaaay pass due my sleepies. Tomorrow is working day, sadly. 😬
@fastidious Okay I _think_ I'm done πŸ˜…

=> [WIP: Improve PostHandler() performance by directly injecting a user's new Twt into the Cache #641](https://git.mills.io/yarnsocial/yarn/pulls/641) @ullarah and I are testing this branch on our pods now 🀞=
@fastidious Okay I _think_ I'm done πŸ˜…

=> [WIP: Improve PostHandler() performance by directly injecting a user's new Twt into the Cache #641](https://git.mills.io/yarnsocial/yarn/pulls/641) @ullarah and I are testing this branch on our pods now 🀞=
Posting on throttled network at ~512kbps.
Test reply, please ignore. :D~
@prologic nice updates!!
@kt84 Hah thanks πŸ˜… I guess nothing is broken so far πŸ˜‚
@kt84 Hah thanks πŸ˜… I guess nothing is broken so far πŸ˜‚
Hmmm did my reply show up on this Yarn immediately or not? Hmmm πŸ€”
Hmmm did my reply show up on this Yarn immediately or not? Hmmm πŸ€”
Let's see how this one goes. Now testing it on desktop. Will try mobile next.
It was relatively slow on desktop, let’s see on mobile. I am not sure if I am running the right branch though…
Alright, I wasn't, but now I am. Testing this again. This is on desktop.
Oh yes, super fast! πŸŽ‰
@fastidious Cool πŸ‘
@fastidious Cool πŸ‘