🧮 USERS:1 FEEDS:2 TWTS:1051 ARCHIVED:77202 CACHE:2435 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1050 ARCHIVED:77116 CACHE:2393 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1049 ARCHIVED:77084 CACHE:2367 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1048 ARCHIVED:77055 CACHE:2368 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1047 ARCHIVED:77046 CACHE:2367 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1046 ARCHIVED:77041 CACHE:2387 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1045 ARCHIVED:77037 CACHE:2387 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1044 ARCHIVED:77033 CACHE:2384 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1043 ARCHIVED:77022 CACHE:2381 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1042 ARCHIVED:77001 CACHE:2369 FOLLOWERS:17 FOLLOWING:14
./tools/dump_cache.sh: line 8: bat: command not found
No Token Provided
I don’t have bat on my VPS and there is no package for installing it. Is cat a reasonable alternate?
🧮 USERS:1 FEEDS:2 TWTS:1041 ARCHIVED:76918 CACHE:2303 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1040 ARCHIVED:76910 CACHE:2313 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1039 ARCHIVED:76897 CACHE:2317 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1038 ARCHIVED:76887 CACHE:2330 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1037 ARCHIVED:76878 CACHE:2329 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1036 ARCHIVED:76865 CACHE:2323 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1035 ARCHIVED:76839 CACHE:2315 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1034 ARCHIVED:76828 CACHE:2318 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1033 ARCHIVED:76801 CACHE:2325 FOLLOWERS:17 FOLLOWING:14
It took me so long to find the cause of a memory leak in GoBlog. I thought it was smart to use a cache for prepared database statements. But I didn’t read the documentation and didn’t know that prepared statements need to be closed when they are no longer needed to free up the allocated resources. 🤦♂️ I finally fixed it by removing the prepared statement cache altogether. Less code, fewer problems in the future, and the cache wasn’t much of an improvement anyway. I also learned about the usefulness of memory profil … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1032 ARCHIVED:76781 CACHE:2307 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1031 ARCHIVED:76765 CACHE:2327 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1030 ARCHIVED:76734 CACHE:2313 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1029 ARCHIVED:76716 CACHE:2297 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1028 ARCHIVED:76704 CACHE:2286 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1027 ARCHIVED:76691 CACHE:2276 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1026 ARCHIVED:76681 CACHE:2276 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1025 ARCHIVED:76659 CACHE:2295 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1024 ARCHIVED:76644 CACHE:2287 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1023 ARCHIVED:76626 CACHE:2279 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1022 ARCHIVED:76617 CACHE:2289 FOLLOWERS:17 FOLLOWING:14
以 Go 語言爲例解釋什麼是僞共享以及如何解決
本文翻譯自:What’s false sharing and how to solve it (using Golang as example)譯文在解釋僞共享(false sharing)之前,有必要簡要介紹一下 CPU 架構中緩存是如何工作的。CPU 緩存中的最小單位是緩存行(cache line)(如今,CPU 中常見的緩存行大小爲 64 字節)。因此,當 CPU 從內存讀取一個變量時, ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1021 ARCHIVED:76613 CACHE:2295 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1020 ARCHIVED:76602 CACHE:2300 FOLLOWERS:17 FOLLOWING:14
go-cache: 採用 Cache-Aside 模式的多層 Go 緩存
在現代的應用程序開發中,緩存是提高性能和擴展性的關鍵技術之一。在 Go 語言的生態系統中,有許多優秀的緩存庫,其中之一便是go-cache。本文將詳細介紹go-cache庫及其使用方法,旨在幫助開發者更好地利用緩存提高應用程序的性能。什麼是 go-cache?————-go-cache是一個靈活的多層緩存庫,設計用於處理內存緩存和共享緩存。它採用了 Cache-Aside(旁路緩存 ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:1019 ARCHIVED:76587 CACHE:2319 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1018 ARCHIVED:76573 CACHE:2313 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1017 ARCHIVED:75609 CACHE:2312 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1016 ARCHIVED:75590 CACHE:2342 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1015 ARCHIVED:75561 CACHE:2359 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1014 ARCHIVED:75547 CACHE:2361 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1013 ARCHIVED:75529 CACHE:2382 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1012 ARCHIVED:75282 CACHE:2384 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1011 ARCHIVED:74318 CACHE:2383 FOLLOWERS:17 FOLLOWING:14
@bender@twtxt.net He is running on the latest macbook pro with 128G memory. though the chrome app seems to be sitting at 125MB. i am a bit suspicious about that stat since we dont see all the worker threads and he is currently sitting on 40GB of non cache ram.
🧮 USERS:1 FEEDS:2 TWTS:1010 ARCHIVED:74279 CACHE:2402 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1009 ARCHIVED:74264 CACHE:2400 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1008 ARCHIVED:74244 CACHE:2398 FOLLOWERS:17 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:1007 ARCHIVED:74229 CACHE:2387 FOLLOWERS:17 FOLLOWING:14