Reddit Programming
191 subscribers
1.22K photos
127K links
I will send you newest post from subreddit /r/programming
Download Telegram
The unlikely Linux macro
https://www.reddit.com/r/programming/comments/1vvrbyb/the_unlikely_linux_macro/

<!-- SC_OFF -->Wrote a bit about the `unlikely` and `likely` macros in the Linux codebase. Great little exploration into tiny optimizations that everyone should know more about 😄 <!-- SC_ON --> submitted by /u/chaobang (https://www.reddit.com/user/chaobang)
[link] (https://rushed-reflections.bearblog.dev/an-unlikely-experiment/) [comments] (https://www.reddit.com/r/programming/comments/1vvrbyb/the_unlikely_linux_macro/)
Running a Java Spring Boot app on a 512 MB VPS with lightweight monitoring
https://www.reddit.com/r/programming/comments/1vxl0w4/running_a_java_spring_boot_app_on_a_512_mb_vps/

<!-- SC_OFF -->I wanted to see how a fairly representative Java Spring Boot application behaves on a very small VPS, especially the difference between configured heap and actual JVM process memory. The test app uses Spring Boot 3.5.x, Spring MVC, JPA/Hibernate, H2, embedded Tomcat, Actuator, scheduled work, and outbound HTTP. I also kept lightweight monitoring on the same machine. The original 256 MB configuration was too tight. With 512 MB RAM + 256 MB swap, the application completed the test reliably. Full setup and measurements are in the linked article. Since then I’ve also managed to get the same application working on a 256 MB VPS with swap using JDK 25 Compact Object Headers and tighter JVM settings. I’m preparing that as a separate follow-up experiment. <!-- SC_ON --> submitted by /u/fykup (https://www.reddit.com/user/fykup)
[link] (https://pvrlabs.xyz/articles/spring-boot-512mb-vps.html) [comments] (https://www.reddit.com/r/programming/comments/1vxl0w4/running_a_java_spring_boot_app_on_a_512_mb_vps/)
GitHub confirms Actions outage caused by database issue
https://www.reddit.com/r/programming/comments/1vz0z6b/github_confirms_actions_outage_caused_by_database/

<!-- SC_OFF -->If your GitHub Actions jobs are stuck in "Queued" or waiting for a runner, GitHub has now confirmed there is an incident. GitHub says they identified an issue with a database primary and are failing over to a replica. Actions is affected, and GitHub Pages is also experiencing degraded performance. So if you have been checking your workflow, runner settings, permissions or billing, it might not be your configuration. Status page: https://www.githubstatus.com/incidents/y1t7p9fzrlj2 Hopefully this saves someone else from spending an hour debugging their YAML. <!-- SC_ON --> submitted by /u/Codeblix_Ltd (https://www.reddit.com/user/Codeblix_Ltd)
[link] (https://www.githubstatus.com/incidents/y1t7p9fzrlj2) [comments] (https://www.reddit.com/r/programming/comments/1vz0z6b/github_confirms_actions_outage_caused_by_database/)
How Jekyll Works
https://www.reddit.com/r/programming/comments/1vztl74/how_jekyll_works/

<!-- SC_OFF -->I like Jekyll a lot. Hope you find it useful. If you notice any errors or have thoughts to share, don't hold back in the comments or DMs. All feedback is genuinely welcome 🙂. <!-- SC_ON --> submitted by /u/sarans22 (https://www.reddit.com/user/sarans22)
[link] (https://sarans.so/articles/how_jekyll_works) [comments] (https://www.reddit.com/r/programming/comments/1vztl74/how_jekyll_works/)