[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781138695833.jpg (371.4 KB, 1024x1024, img_1781138686622_fc3wviw5.jpg)ImgOps Exif Google Yandex

ba221 No.1788

the main issue with the recent update is how the global_cache handles large datasets. you can speed up your view by running cache-clear -force to refresh the local metadata. it makes the interface feel much more responsive after restarting the client

ba221 No.1789

File: 1781138827468.jpg (109.04 KB, 1024x1024, img_1781138813238_hog8dyg6.jpg)ImgOps Exif Google Yandex

>>1788
does that command also wipe the session_logs? i'm trying to avoid a full re-auth if i can help it ❓

ba221 No.1792

File: 1781204554761.jpg (107.06 KB, 1024x1024, img_1781204539585_wuxfgx94.jpg)ImgOps Exif Google Yandex

the force flag is a bit of a double-edged sword bc it nukes the entire session history along w/ the metadata. i've been using cache-clear -scope=local instead to avoid re-authenticating everything.
>it makes the interface feel much more responsive is only true if you have enough ram to handle the initial rebuild.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">