dybr

 In the morning I was feeling so good, started to do this memory leak tracking.

Tweaked the logging a little bit, and found that there are two sorts of leak:

- when requests are coming, there's at least several megs gobbled per request

- when the server is idle, every 40 seconds it eats between half a meg and a meg.

Ok, now what. Now i need a profiler. So I'm trying to figure out Java Flight Recorder, following hardly readable Oracle documentation. By "hardly readable" I mean they have gray font on white. Why? It's probably about Larry, who else. Have to ask Andrew maybe. Or Dima. Or... no, not Sandeep. We kind of hate each other.

Anyway, and we had a standup, then a planning meeting; I said it will take between 3 and 5 "points" to find and fix the leak. I could not say "4 points", because we don't have that coin. Only 1,2,3,5.

I actually fell asleep during the planning meeting. Thank god my cam and mic were turned off.

Later I woke up and worked with JFR. We will see. I also asked Jacob if we can purchase "ultimate" IntelliJ. He'll investigate.

There's also JProfiler (still alive), I worked with him for a bunch of years. But I would prefer IntelliJ, and I'm curious about JFR.

Our noobs are really cool, especially this North Carolina man (there are no guys or. dudes in Carolinas). That's how I liked him during the interview: he's an enthusiast. I love enthusiasts. At times they break things (sigh, I was wrong when I fired JEF for breaking our Forth...).

Anyway, I'm still under jet lag, so not exactly behaving reasonably. If you could know how hard it was to do my daily dose of French.

Ok, an update. I decided to to runtime.gc() every 10 seconds.

Problem GONE.

So it's all about JVM parameters regarding gc behavior. No big deal to fix; and even I don't fix it, I can just run this gc thread every 10 seconds. Big deal, really.

How come I, a functional Scala programmer, am supposed to do these devops things, I wonder. But ain't it funny?