Skip to content

Instantly share code, notes, and snippets.

@ceroloy
ceroloy / prometheus_memory_utilization_investigation.md
Last active December 29, 2021 08:38
Prometheus Memory Usage Investigation

To understand the proper memory limits for Prometheus, we first need to observe the memory usage behavior of the deployment. After the increase in memory, we can clearly see the reported usage doesn't decrease but oscillate around new level. This is an unexpected behavior, and why the RSS memory is not released after the increase needs to be investigated. Keep in mind that this pattern was initially observed in only one region.

Current configuration:

  • Version 2.18.1
  • GoVersion go1.14.2
  • Prometheus Helm Chart: v11.5.0

Screenshot from 2021-10-29 10-51-10

@melklein
melklein / vim_solutions.md
Last active July 6, 2016 10:39
useful vim commands
  • increase number under cursor: ctrl+a
  • decrease number under cursor: ctrl+x
  • replace one word with another: select first word, e.g. vi"; select second word vi" and paste p
  • search from within vim, don't jump to first match: vimgrep /render_show/gj **/*.rb

Resize splits

  • resize horizontal split: ctrl+w - / ctrl+w +
  • resize horizontal split to maximum: ctrl+w _
  • make horizontal and vertical splits equally big: ctrl+w =
  • resize vertical split: ctrl+w < / ctrl+w >
@chitchcock
chitchcock / 20111011_SteveYeggeGooglePlatformRant.md
Created October 12, 2011 15:53
Stevey's Google Platforms Rant

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real