3 ms·

Setting up graylog was one of the worst mistakes I made. It took forever to get all the required software installed and configured and then it was taking up all

Setting up graylog was one of the worst mistakes I made. It took forever to get all the required software installed and configured and then it was taking up all the ram on the server doing fuck all.

SteveNuts 8y ago
That was just Java doing Java things. Business as usual.
- RhodesianHunter 8y ago
  This is a nonsense comment doing language troll things.
deleted 8y ago
[deleted]
atm0sphere 8y ago
There were single script 1-click installs for it in bash all over for me..but yeah jvm is a hog.
- yjftsjthsd-h 8y ago
  My experience with those one-liner installs is that they usually work... strictly speaking. They don't scale, they don't deal with edge cases, they know nothing of your environment. They install one piece of software (in an "interesting" way that won't upgrade), and that's it.
  - sunnymanokl 8y ago
    My last pay check was $9500 working 12 hours a week online. My sisters friend has been averaging 15k for months now and she works about 20 hours a week. I can't believe how easy it was once I tried it out. This is what I do, HERE►► http://www.worktoday33.com http://www.worktoday33.com
  - sunnymanokl 8y ago
    ZZ
- ATsch 8y ago
  I think "jvm is a hog" misattribution is actually part of the cause of "jvm being a hog". It implies that you don't need to worry about your memory management and efficiency in Java, because any hoggyness is the jvm's fault. With GC, you can just get away with having memory leaks everywhere and allocate millions of objects per second without any catastropic consequences. JVM software written with knowledge of memory management and that allocation isn't free can perform just as well as any other platform. As Bryan Cantrill loves to say in ever single talk: "gc is not your problem, allocation is your problem, GC just defers the cost".

3 ms·

Setting up graylog was one of the worst mistakes I made. It took forever to get all the required software installed and configured and then it was taking up all

by baroffoos 8y ago

Setting up graylog was one of the worst mistakes I made. It took forever to get all the required software installed and configured and then it was taking up all the ram on the server doing fuck all.

SteveNuts 8y ago
That was just Java doing Java things. Business as usual.
- RhodesianHunter 8y ago
  This is a nonsense comment doing language troll things.
deleted 8y ago
[deleted]
atm0sphere 8y ago
There were single script 1-click installs for it in bash all over for me..but yeah jvm is a hog.
- yjftsjthsd-h 8y ago
  My experience with those one-liner installs is that they usually work... strictly speaking. They don't scale, they don't deal with edge cases, they know nothing of your environment. They install one piece of software (in an "interesting" way that won't upgrade), and that's it.
  - sunnymanokl 8y ago
    My last pay check was $9500 working 12 hours a week online. My sisters friend has been averaging 15k for months now and she works about 20 hours a week. I can't believe how easy it was once I tried it out. This is what I do, HERE►► http://www.worktoday33.com http://www.worktoday33.com
  - sunnymanokl 8y ago
    ZZ
- ATsch 8y ago
  I think "jvm is a hog" misattribution is actually part of the cause of "jvm being a hog". It implies that you don't need to worry about your memory management and efficiency in Java, because any hoggyness is the jvm's fault. With GC, you can just get away with having memory leaks everywhere and allocate millions of objects per second without any catastropic consequences. JVM software written with knowledge of memory management and that allocation isn't free can perform just as well as any other platform. As Bryan Cantrill loves to say in ever single talk: "gc is not your problem, allocation is your problem, GC just defers the cost".