Phil
I really doubt this is what fixed it, but in docker-compose.yml I changed:
- RUST_LOG="warn"
to
- RUST_LOG="warn,lemmy_server=debug,lemmy_api=debug,lemmy_api_common=debug,lemmy_api_crud=debug,lemmy_apub=debug,lemmy_db_schema=debug,lemmy_db_views=debug,lemmy_db_views_actor=debug,lemmy_db_views_moderator=debug,lemmy_routes=debug,lemmy_utils=debug,lemmy_websocket=debug"
- RUST_BACKTRACE=full
(got the latter from the sample docker-compose.yml on GitHub).
Is anyone else seeing super high CPU usage after updating? The docker container seems to spawn a ton of lemmy_server processes, each eating up 50-100% of a core. I don’t see anything suspicious in the logs though, it just calmly processes posts.
I found this website to be pretty helpful in terms of walking you through a docker- based install:
The official docs are a little sparse at times.
Super straightforward upgrade via docker compose, thanks for all the hard work ❤️
Ah ok. I’m on iOS so there is no dedicated back button. Regarding the lag: I do have the issue where if I swipe to go back, I can’t resume scrolling immediately. It takes a split second for the scrolling to be responsive again. Not sure if that’s the lag you meant. The thing I’m describing is apparently a safari bug: