I've narrowed the cause of the CPU spike to a specific few of our unit tests. During the spike period, the gradle process output goes through the roof. The output is composed almost entirely of lines like this:
13:54:24.263 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClient] Received object #43395, type: org.gradle.logging.internal.LogEvent 13:54:22.635 [DEBUG] [org.gradle.messaging.remote.internal.WorkerProtocol] Dispatching request to worker: [Request consumer: 26ae4489-bcfc-4ed4-b796-15e83aae0dee, payload: [MethodInvocation method: output()]] For the problem tests, there are over 7 million of these lines vs hundreds for non problem tests. -- View this message in context: http://gradle.1045684.n5.nabble.com/Gradle-daemon-160-CPU-usage-during-long-test-run-tp5124315p5126870.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
