From c99b5ddfaab88b8f179dce94793005ad1d93ec6a Mon Sep 17 00:00:00 2001
From: Damian Gryski <damian@gryski.com>
Date: Tue, 13 Mar 2018 20:40:13 -0700
Subject: [PATCH] point to filled out time.Parse() section

---
 performance.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/performance.md b/performance.md
index dedefe3..939742b 100644
--- a/performance.md
+++ b/performance.md
@@ -596,8 +596,7 @@ improve allowing you to stop when you hit an acceptable limit.
 Cache common cases:
 
 * Your cache doesn't even need to be huge.
-* Optimized a log processing script to cache the previous time passed to
-  `time.Parse()` for significant speedup.
+  * see `time.Parse() example below; just a single value made an impact
 * But beware cache invalidation, thread issues, etc.
 * Random cache eviction is fast and sufficiently effective.
 * Random cache insertion can limit cache to popular items with minimal logic.