home.social

#footimac — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #footimac, aggregated by home.social.

fetched live
  1. @EdwinG ya I only have 1 thread ever stuck it seems, so I’m not too worried about it. @jfmezei found a very relevant bugreport relating to latency which would make sense. Worst case scenario, I could move the redis container back onto #footiMac. That should take the latency down to near zero.

  2. @EdwinG ya I only have 1 thread ever stuck it seems, so I’m not too worried about it. @jfmezei found a very relevant bugreport relating to latency which would make sense. Worst case scenario, I could move the redis container back onto #footiMac. That should take the latency down to near zero.

  3. @EdwinG ya I only have 1 thread ever stuck it seems, so I’m not too worried about it. @jfmezei found a very relevant bugreport relating to latency which would make sense. Worst case scenario, I could move the redis container back onto #footiMac. That should take the latency down to near zero.

  4. @EdwinG ya I only have 1 thread ever stuck it seems, so I’m not too worried about it. @jfmezei found a very relevant bugreport relating to latency which would make sense. Worst case scenario, I could move the redis container back onto #footiMac. That should take the latency down to near zero.

  5. @EdwinG ya I only have 1 thread ever stuck it seems, so I’m not too worried about it. @jfmezei found a very relevant bugreport relating to latency which would make sense. Worst case scenario, I could move the redis container back onto #footiMac. That should take the latency down to near zero.

  6. @jfmezei this is good info. It would make sense that I increased the latency by moving the redis work across the continent. So if latency impacts the scheduler that would make sense. I am not too worried because I never see more than one busy thread at a time in the scheduler queues so it doesn't seem to be a critical issue. But if it does become an issue, I could try moving the redis docker container back onto #footiMac. It's less than 1GB so it's easy to move around and doesn't add a lot to the impact on the old mac.

  7. @jfmezei this is good info. It would make sense that I increased the latency by moving the redis work across the continent. So if latency impacts the scheduler that would make sense. I am not too worried because I never see more than one busy thread at a time in the scheduler queues so it doesn't seem to be a critical issue. But if it does become an issue, I could try moving the redis docker container back onto #footiMac. It's less than 1GB so it's easy to move around and doesn't add a lot to the impact on the old mac.

  8. @jfmezei this is good info. It would make sense that I increased the latency by moving the redis work across the continent. So if latency impacts the scheduler that would make sense. I am not too worried because I never see more than one busy thread at a time in the scheduler queues so it doesn't seem to be a critical issue. But if it does become an issue, I could try moving the redis docker container back onto #footiMac. It's less than 1GB so it's easy to move around and doesn't add a lot to the impact on the old mac.

  9. @jfmezei this is good info. It would make sense that I increased the latency by moving the redis work across the continent. So if latency impacts the scheduler that would make sense. I am not too worried because I never see more than one busy thread at a time in the scheduler queues so it doesn't seem to be a critical issue. But if it does become an issue, I could try moving the redis docker container back onto #footiMac. It's less than 1GB so it's easy to move around and doesn't add a lot to the impact on the old mac.

  10. @jfmezei this is good info. It would make sense that I increased the latency by moving the redis work across the continent. So if latency impacts the scheduler that would make sense. I am not too worried because I never see more than one busy thread at a time in the scheduler queues so it doesn't seem to be a critical issue. But if it does become an issue, I could try moving the redis docker container back onto #footiMac. It's less than 1GB so it's easy to move around and doesn't add a lot to the impact on the old mac.

  11. Here’s a #mastoadmin #selfhost question.

    Why would the scheduler process be up around 1000 seconds for average completion time when all others are under 5 seconds?

    Is it something to be concerned about?

    #footiMac #debian #mastodon

  12. Here’s a #mastoadmin #selfhost question.

    Why would the scheduler process be up around 1000 seconds for average completion time when all others are under 5 seconds?

    Is it something to be concerned about?

    #footiMac #debian #mastodon

  13. Here’s a #mastoadmin #selfhost question.

    Why would the scheduler process be up around 1000 seconds for average completion time when all others are under 5 seconds?

    Is it something to be concerned about?

    #footiMac #debian #mastodon

  14. Here’s a #mastoadmin #selfhost question.

    Why would the scheduler process be up around 1000 seconds for average completion time when all others are under 5 seconds?

    Is it something to be concerned about?

    #footiMac #debian #mastodon

  15. Here’s a #mastoadmin #selfhost question.

    Why would the scheduler process be up around 1000 seconds for average completion time when all others are under 5 seconds?

    Is it something to be concerned about?

    #footiMac #debian #mastodon

  16. Oooh. And it dawned on me that since there is no db and redis taking up space on #footiMac I could probably add another set of processes, so I am up to 3 processes now with 15 queues each doing the push/pull/ingress/default which helps keep the latency down!

    FootiMac feeling snappy again!

    #selfhost #mastodon #docker #debian

  17. Oooh. And it dawned on me that since there is no db and redis taking up space on #footiMac I could probably add another set of processes, so I am up to 3 processes now with 15 queues each doing the push/pull/ingress/default which helps keep the latency down!

    FootiMac feeling snappy again!

    #selfhost #mastodon #docker #debian

  18. Oooh. And it dawned on me that since there is no db and redis taking up space on #footiMac I could probably add another set of processes, so I am up to 3 processes now with 15 queues each doing the push/pull/ingress/default which helps keep the latency down!

    FootiMac feeling snappy again!

    #selfhost #mastodon #docker #debian

  19. Oooh. And it dawned on me that since there is no db and redis taking up space on #footiMac I could probably add another set of processes, so I am up to 3 processes now with 15 queues each doing the push/pull/ingress/default which helps keep the latency down!

    FootiMac feeling snappy again!

    #selfhost #mastodon #docker #debian

  20. Oooh. And it dawned on me that since there is no db and redis taking up space on #footiMac I could probably add another set of processes, so I am up to 3 processes now with 15 queues each doing the push/pull/ingress/default which helps keep the latency down!

    FootiMac feeling snappy again!

    #selfhost #mastodon #docker #debian

  21. by jove. i think we have liftoff!

    #footiMac is now doing the webserver and other frontend mastodon stuff while passing the redis and db functions to my external host running docker containers monitored in portainer!

    not too shabby!

    #selfhost #mastodon #docker #debian

  22. by jove. i think we have liftoff!

    #footiMac is now doing the webserver and other frontend mastodon stuff while passing the redis and db functions to my external host running docker containers monitored in portainer!

    not too shabby!

    #selfhost #mastodon #docker #debian

  23. by jove. i think we have liftoff!

    #footiMac is now doing the webserver and other frontend mastodon stuff while passing the redis and db functions to my external host running docker containers monitored in portainer!

    not too shabby!

    #selfhost #mastodon #docker #debian

  24. by jove. i think we have liftoff!

    #footiMac is now doing the webserver and other frontend mastodon stuff while passing the redis and db functions to my external host running docker containers monitored in portainer!

    not too shabby!

    #selfhost #mastodon #docker #debian

  25. by jove. i think we have liftoff!

    #footiMac is now doing the webserver and other frontend mastodon stuff while passing the redis and db functions to my external host running docker containers monitored in portainer!

    not too shabby!

    #selfhost #mastodon #docker #debian

  26. well *&^t… it worked on the first try!

    REDIS now hosted from my external (leasedweb) host!
    #portainer #selfhost #mastoadmin #footiMac

  27. well *&^t… it worked on the first try!

    REDIS now hosted from my external (leasedweb) host!
    #portainer #selfhost #mastoadmin #footiMac

  28. well *&^t… it worked on the first try!

    REDIS now hosted from my external (leasedweb) host!
    #portainer #selfhost #mastoadmin #footiMac

  29. well *&^t… it worked on the first try!

    REDIS now hosted from my external (leasedweb) host!
    #portainer #selfhost #mastoadmin #footiMac

  30. well *&^t… it worked on the first try!

    REDIS now hosted from my external (leasedweb) host!
    #portainer #selfhost #mastoadmin #footiMac

  31. trying out #portainer to run docker on my external host and... possibly... move my redis and db containers to the external.

    trying to move redis first!

    the portainer interface is not bad.
    #selfhost #mastoadmin #footiMac

  32. trying out #portainer to run docker on my external host and... possibly... move my redis and db containers to the external.

    trying to move redis first!

    the portainer interface is not bad.
    #selfhost #mastoadmin #footiMac

  33. trying out #portainer to run docker on my external host and... possibly... move my redis and db containers to the external.

    trying to move redis first!

    the portainer interface is not bad.
    #selfhost #mastoadmin #footiMac

  34. trying out #portainer to run docker on my external host and... possibly... move my redis and db containers to the external.

    trying to move redis first!

    the portainer interface is not bad.
    #selfhost #mastoadmin #footiMac

  35. trying out #portainer to run docker on my external host and... possibly... move my redis and db containers to the external.

    trying to move redis first!

    the portainer interface is not bad.
    #selfhost #mastoadmin #footiMac

  36. just separated the stream and mastodon services a little by having the webcams send to the #newIMac ’s wifi address instead of the same ethernet address everything else is using.

    Hopefully that stabilizes things a little. The whole machine seemed to be losing its connectivity periodically, which made things freak out and eventually die.

    #Selfhost #FootiMac

  37. just separated the stream and mastodon services a little by having the webcams send to the #newIMac ’s wifi address instead of the same ethernet address everything else is using.

    Hopefully that stabilizes things a little. The whole machine seemed to be losing its connectivity periodically, which made things freak out and eventually die.

    #Selfhost #FootiMac

  38. just separated the stream and mastodon services a little by having the webcams send to the #newIMac ’s wifi address instead of the same ethernet address everything else is using.

    Hopefully that stabilizes things a little. The whole machine seemed to be losing its connectivity periodically, which made things freak out and eventually die.

    #Selfhost #FootiMac

  39. just separated the stream and mastodon services a little by having the webcams send to the #newIMac ’s wifi address instead of the same ethernet address everything else is using.

    Hopefully that stabilizes things a little. The whole machine seemed to be losing its connectivity periodically, which made things freak out and eventually die.

    #Selfhost #FootiMac

  40. just separated the stream and mastodon services a little by having the webcams send to the #newIMac ’s wifi address instead of the same ethernet address everything else is using.

    Hopefully that stabilizes things a little. The whole machine seemed to be losing its connectivity periodically, which made things freak out and eventually die.

    #Selfhost #FootiMac

  41. @EdwinG complete and successful at 14:40.

    So that's 35 minutes on old #footiMac

  42. @EdwinG complete and successful at 14:40.

    So that's 35 minutes on old #footiMac

  43. @EdwinG complete and successful at 14:40.

    So that's 35 minutes on old #footiMac

  44. @EdwinG complete and successful at 14:40.

    So that's 35 minutes on old #footiMac

  45. @EdwinG complete and successful at 14:40.

    So that's 35 minutes on old #footiMac