January 2018
Cut garbage collection to 2.4% of CPU on a fraud service.
Events, most recent first
- January 2018Cut garbage collection to 2.4% of CPU on a fraud serviceI profiled a fraud-prevention service, found it spent about 17.7% of CPU on garbage collection, tuned the JVM to bring that to 2.4%, and showed the team the before-and-after evidence.Project
- January 2018Owned a hardware clean-up that moved fraud services to new-generation hosts and saved about $23,800 a yearProject
