# 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 1
# self = https://watcher.sour.is/conv/x6bovja
yue-fang-readfog-go
feeds.twtxt.net
View Thread
瞬間高併發，goroutine 執行結束後的資源佔用問題**
問題--當 Go 系統遭遇突增流量，洪峯過境，流量恢復正常後，整個系統的資源消耗是否會變大?第一反應，應該是會恢復到之前的水平吧！資源消耗在流量恢復正常之後，爲什麼會變大呢... 復現-- 模擬一下該場景。我們知道 Go 原生的網絡模型 goroutine-per-connection，即一個連接分配一個 goroutine 去處理。當流量突增，瞬間高併發，很有可能使協程數量也同步增加。即如 ⌘ Read more