Re:An ex-Googler’s guide to dev tools
by jeffbee on Thursday November 26, 2020 @10:44AM
(#25220930)
Interesting. Viceroy can put way more pixels on the screen than grafana with the same cpu and memory usage, and panopticon is specifically written to send little traffic over the wire, so it’s useful to an oncall engineer over a poor mobile backhaul like GPRS. Grafana is a massive resource hog in all dimensions.
[ Parent
| on HN ]
Re:An ex-Googler’s guide to dev tools
by rockwotj on Thursday November 26, 2020 @12:24PM
(#25221890)
Hasn't pcon been deprecated for a year and a half now? :P
More pixels != to more information. The visuals and varieties in ways to present data in grafana always seemed more intuitive for me, being able to lay stuff out in different ways was great. I worked on a G-on-G project at Google and used both grafana and viceroy. I never had an issue with grafana on mobile, but I was never was able to see viceroy on a mobile browser because of the Corp network.
On viceroy if you unintentionally put 2000 lines on a graph, you get a visual mess. If you do that on grafana your tab will hang for ten minutes. Big difference.
Re:An ex-Googler’s guide to dev tools
by rockwotj on Thursday November 26, 2020 @03:15PM
(#25223205)
True, but that only happens when setting up graphs. Graphs are not changed as often as they are viewed.
I'm sure viceroy is more performant, and I'm not denying that, I may also be scarred a bit because I found writing mash queries an arcane nightmare, and those are related to viceroy.
The default (rpc latencies and etc) views and metrics you get are amazing however.
Re:An ex-Googler’s guide to dev tools
by joshuamorton on Thursday November 26, 2020 @03:26PM
(#25223276)
You can also get tons of lines when modifying group by expressions, which you can do ineffectively.
Mash is indeed arcane, although gmon (viceroy) makes it worse than usual.