3 ms·

Does not seem to affect Europe. In fact, right now YouTube loads far quicker than it has for the last seven to ten days, where it would take ages to load any Y

by dom0 9y ago

Does not seem to affect Europe. In fact, right now YouTube loads far quicker than it has for the last seven to ten days, where it would take ages to load any YouTube page.

trhway 9y ago
reboot helps. May be Google runs Windows. Then they just need to reboot more frequently, ie. proactively.
- aneutron 9y ago
  [Removed]
  - flavio81 9y ago
    There is a common practice for Node.js developers to use one of those tools that automatically reboot the site either whenever the single-threaded-event-loop-server crashes, or periodically...
    - mayank 9y ago
      While this pattern is common in node, it's not node specific. Erlang/OTP uses supervised process trees, Linux has supervisord to support this pattern, and the general idea is called "crash-only" software [1], among other names. [1] https://en.m.wikipedia.org/wiki/Crash-only_software https://en.m.wikipedia.org/wiki/Crash-only_software
    - detaro 9y ago
      Assuming you don't mean full "reboot", but reloading/restarting the app runtime every X requests, that's not unusual in many languages. Helps against memory leaks (which are not necessarily the fault of the application and thus not always fixable)
- 21 9y ago
  Funnily enough, in one previous company I worked, which used Linux exclusively, the software was very buggy, and the servers were rebooted daily. We jokingly called that the "Windows solution". When we proposed adding a daily reboot to cron, the tech lead (which encouraged practices which lead to this low quality software) retorted that "this in not Windows, it doesn't need constant reboots", totally missing the point that just using Linux doesn't make you a developer of reliable software.
  - noir_lord 9y ago
    I used to have a service that was like that, it was third party and only handled a specific function so I had a cron job that would reboot it at 4am every day. Sometimes the hammer approach is the only solution.
    - ianai 9y ago
      Was the software loading kernel modules? I'm curious why a more simple kill process routine wouldn't work.
      - LoSboccacc 9y ago
        Having been in a similar situation, many enterprise software require a precise start order and shutdown, sometime even depending to certain system services or some arcane stuff that then breaks in unpredictable times and often the only sane way to restart the environment is to bring it down whole
        noir_lord 9y ago
        Exactly this, it was a horrible piece of enterprise software that depended on other similary horrible pieces of crap. The only way to get it into a known good state when it shit the bed was to reboot the machine and then let it sort itself out. We rapidly moved away from using it. Funnily enough I'm in a similar situation at the new job with Jasper Reports, god damn if that thing isn't everything bad about Enterprise Java(TM).
- emidln 9y ago
  Jaded developer here: a cronjob `pkill -9 foo` is cheaper than debugging a memory leak for a lot of businesses. Let the process supervisor handle the process death.

by dom0 9y ago

Does not seem to affect Europe. In fact, right now YouTube loads far quicker than it has for the last seven to ten days, where it would take ages to load any YouTube page.

trhway 9y ago

reboot helps. May be Google runs Windows. Then they just need to reboot more frequently, ie. proactively.

aneutron 9y ago
[Removed]
- flavio81 9y ago
  There is a common practice for Node.js developers to use one of those tools that automatically reboot the site either whenever the single-threaded-event-loop-server crashes, or periodically...
  - mayank 9y ago
    While this pattern is common in node, it's not node specific. Erlang/OTP uses supervised process trees, Linux has supervisord to support this pattern, and the general idea is called "crash-only" software [1], among other names. [1] https://en.m.wikipedia.org/wiki/Crash-only_software https://en.m.wikipedia.org/wiki/Crash-only_software
  - detaro 9y ago
    Assuming you don't mean full "reboot", but reloading/restarting the app runtime every X requests, that's not unusual in many languages. Helps against memory leaks (which are not necessarily the fault of the application and thus not always fixable)
21 9y ago
Funnily enough, in one previous company I worked, which used Linux exclusively, the software was very buggy, and the servers were rebooted daily. We jokingly called that the "Windows solution". When we proposed adding a daily reboot to cron, the tech lead (which encouraged practices which lead to this low quality software) retorted that "this in not Windows, it doesn't need constant reboots", totally missing the point that just using Linux doesn't make you a developer of reliable software.
- noir_lord 9y ago
  I used to have a service that was like that, it was third party and only handled a specific function so I had a cron job that would reboot it at 4am every day. Sometimes the hammer approach is the only solution.
  - ianai 9y ago
    Was the software loading kernel modules? I'm curious why a more simple kill process routine wouldn't work.
    - LoSboccacc 9y ago
      Having been in a similar situation, many enterprise software require a precise start order and shutdown, sometime even depending to certain system services or some arcane stuff that then breaks in unpredictable times and often the only sane way to restart the environment is to bring it down whole
      - noir_lord 9y ago
        Exactly this, it was a horrible piece of enterprise software that depended on other similary horrible pieces of crap. The only way to get it into a known good state when it shit the bed was to reboot the machine and then let it sort itself out. We rapidly moved away from using it. Funnily enough I'm in a similar situation at the new job with Jasper Reports, god damn if that thing isn't everything bad about Enterprise Java(TM).
emidln 9y ago
Jaded developer here: a cronjob `pkill -9 foo` is cheaper than debugging a memory leak for a lot of businesses. Let the process supervisor handle the process death.