ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Community

Chat Logs

Thursday, October 15, 2026 (America/New_York)

  1. * nevet joined #repopack
  2. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  3. * nevet joined #repopack
  4. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  5. * nevet joined #repopack
  6. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  7. * nevet joined #repopack
  8. * blue!~blue@user/blue changed the topic to: https://repopack.com | This channel is logged: https://bytecode.news/logs/irc/libera/repopack
  9. * phaleth joined #repopack
  10. phalethI've moved haproxy and dataplane api to a podman container named 000001-repopack-site-haproxy
  11. bluehi phaleth
  12. bluewas that necessary?
  13. phalethyeah, it's easier for repopack to take control over deployment
  14. blueah ok
  15. phalethshould do the same with buildkit next, after that prometheus and grafana
  16. phalethideally only podman and VPN should be installed directly on the OS
  17. bluebtw repopack is now at reliably <300mb
  18. bluebut I'm still profiling it
  19. phalethgreat :)
  20. phaleththat's a huge achievement, how did that happen?
  21. phalethrepopack runtime is up only for 3 hours now
  22. phalethfor VPN I started looking into wireguard, cause it's simple and there are also containers, so in the end it may not end up on host, but not sure
  23. phalethI mean the container can be on host network and then that should be the same, it's just wireguard will be in a container
  24. bluewell I've been profiling and improving stuff in repopack itself mostly
  25. bluewe'll see. I redeploy quite often so that could be masking it
  26. bluebut it reliably stays under 400mb now
  27. phalethok, but do you know what was leaking memory?
  28. phalethyeah
  29. bluehttps://repopack.com/project/repopack/tasks/500
  30. blueseems like SSE was partly to blame
  31. bluethis is still being followed-up
  32. bluehttps://repopack.com/project/repopack/tasks/544?tasks=status%3Dopen
  33. blueI'm not done yet with profiling and optimising
  34. bluebut at the present moment, I think we can safely say primate isn't leaking any memmory
  35. bluememory*
  36. blueand never has, in fact
  37. phalethoh, clanker can do this kinda peeking into the process
  38. phalethyeah, I just call it leaking memory, but you know some kind of stale cache that never clears
  39. * phaleth quit (Quit: phaleth)