<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>hotspot on batmat.net</title>
		<link>https://batmat.net/tags/hotspot/</link>
		<description>Recent content in hotspot on batmat.net</description>
		<generator>Hugo</generator>
		<language>fr-FR</language>
		
		
		
		
			<lastBuildDate>Mon, 17 Oct 2016 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://batmat.net/tags/hotspot/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Always enable GC logs, and how to enable logs rotation with HotSpot</title>
				<link>https://batmat.net/2016/10/17/always-enable-gc-logs-and-how-to-enable-logs-rotation-with-hotspot/</link>
				<pubDate>Mon, 17 Oct 2016 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2016/10/17/always-enable-gc-logs-and-how-to-enable-logs-rotation-with-hotspot/</guid>
				
				<description> Having had recently to refresh my memories and play with some new things about GC logging, I thought that ought to be a good opportunity to dig a bit on it, especially on log rotation.&#xA;Reminder: Always enable GC logging in production If you run a production server, and you don’t have GC logs enabled, DO IT NOW. Really, it could save your ass.&#xA;It is unnoticeable in terms of performance impact, and is invaluable if you need to diagnose some performance issue. It was a bit of a mess with HotSpot many years ago, since log rotation was not available. But now it’s been added for quite a long time, there is no excuse anymore.&#xA;</description>
			</item>
	</channel>
</rss>
