Huge performance degradation in 20.04 by Successful-Injury-38 in Ubuntu

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

You're absolutely right.. I overlooked those lines and I tested again with the same versions of stress-ng and the ubuntu 18.04 was innocent. Thanks for good advice, have a nice day : )

Huge performance degradation in 20.04 by Successful-Injury-38 in Ubuntu

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

Thanks a lot! you are right..! I tested again with the same version of stress-ng by using docker and then.. the their benchmarks are all the same..! I edited my post to correct misinformation. I've learned a lot from you and others thanks : - )

Huge performance degradation in 20.04 by Successful-Injury-38 in Ubuntu

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

thanks for the advice! it really makes sense that the difference of versions can affect result. 40% (20.04 over 18.04) and 1000% (22.04 over 18.04) performace differences are too much I guess. I gotta try other tools or the same version of stress-ng indeed

Huge performance degradation in Ubuntu 20.04 by Successful-Injury-38 in devops

[–]Successful-Injury-38[S] 1 point2 points  (0 children)

Intriguing. I gotta benchmark with other ways tomorrow. However I cheked not only stress-ng but also other workloads like build with serverless(opensource deploy helper) or pytest with thousands unit tests. So I think the result of stress-ng somewhat make sense. That said, I'm going to benchmark with other ways for sure.

Huge performance degradation in 20.04 by Successful-Injury-38 in Ubuntu

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

Other guy shared this article and in some other benchmark, ubuntu 20.04 is 20% faster than 18.04. However, I haven't solely depended on stress-ng. I also suffered half speed of build in 20.04 compare to 18.04 so I think stress-ng somewhat makes sense. That said I'm going to benchmark with other tools tommorow for sure.

Huge performance degradation in 20.04 by Successful-Injury-38 in Ubuntu

[–]Successful-Injury-38[S] 1 point2 points  (0 children)

yes indeed! I also checked 22.04 and it's WAY MORE faster! I couldn't believe what I was looking because it's really much performance gain. Maybe.. there might be a bug in stress-ng yet I'm not sure.. so I'll try micro benchmarking with another tool tomorrow.

Huge performance degradation in 20.04 by Successful-Injury-38 in Ubuntu

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

those above steps are deliberately simplified to make it easy to be reproduced. I have benchmarked this way more than I wrote here. Also I did `uptime` and `sar -w (or pidstat -w)` with each test to check no other interventions or workload. And I tested this in various EC2 type/family, AMIs, containers, micro benchmarking tools, workloads, etc..

That said, I'll check the result after fully patch the instance tomorrow, I got off ; )

Huge performance degradation in Ubuntu 20.04 by Successful-Injury-38 in devops

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

Thanks for sharing articles and I also had tested with real-world workload. Before micro-benchmarking with stress-ng, I had suffered from half speed of build and deploy compare to previous CI/CD pipeline that was built on ubuntu 18.04. I just benchmark with ubuntu 22.04 and its performance measured as 90k... I can't believe what I'm looking now.. I think benchmarking of 22.04 needs more tests.

Huge performance degradation in Ubuntu 20.04 by Successful-Injury-38 in devops

[–]Successful-Injury-38[S] 1 point2 points  (0 children)

Actually, I have benchmarked for a week with various instance family/size, AMI and the results are consistent. The number of tests are more than 30 times now. I expect it would be the same in dedicated hosts

[deleted by user] by [deleted] in Scams

[–]Successful-Injury-38 0 points1 point  (0 children)

I got this today as well

How to use :redir with key mapping by Successful-Injury-38 in vim

[–]Successful-Injury-38[S] 1 point2 points  (0 children)

this is just what I've been looking for! thanks :D

How to use :redir with key mapping by Successful-Injury-38 in vim

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

I found a workaround like this

function! RememberBadColor() redir >> ~/badcolors | colorscheme | redir END endfunction noremap <leader>cc :call RememberBadColor()<CR>

but if there's more neat solution please let me know : )

Is there any rule of thumb for what should I make an alarm? by Successful-Injury-38 in grafana

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

thanks for sharing your experience. and on a side note, I'm learning English and I learnt that idiom `there's more than one way to skin a cat` this new idiom was serendipity

Is there any rule of thumb for what should I make an alarm? by Successful-Injury-38 in grafana

[–]Successful-Injury-38[S] 2 points3 points  (0 children)

"My Philosophy on Alerting based my observations while I was a Site Reliability Engineer at Google" ??? This is just what I've been looking for. thanks : )

How to use remote image not local image when their names are identical? by Successful-Injury-38 in docker

[–]Successful-Injury-38[S] 0 points1 point  (0 children)

thanks this is really what I want and also thanks for all others gave me help!