[
https://issues.apache.org/jira/browse/CALCITE-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173471#comment-17173471
]
Julian Hyde commented on CALCITE-4168:
--------------------------------------
[~vladimirsitnikov], I am not sure exactly what is going on, but I run about a
dozen test jobs per night on my home Linux server, and recently the jobs have
started to hang and run out of memory. When I get to the machine in the
morning, it is quite common for it to have a 10GB swap file, unresponsive for 5
minutes. There are out-of-memory errors from the Gradle daemons.
I am loathe to start debugging these issues, but they are new over the last
month or two.
Please be very careful what you introduce. Your changes have the potential to
make things a few percent better, but they also have the potential to make
things a lot worse.
I don't want to spend several hours diagnosing problems. Heck, I don't want to
learn about Gradle daemons or build cache. I would rather my builds are simple
and predictable and take a few seconds longer.
> Configure Gradle Remote Build Cache to speedup builds
> -----------------------------------------------------
>
> Key: CALCITE-4168
> URL: https://issues.apache.org/jira/browse/CALCITE-4168
> Project: Calcite
> Issue Type: Task
> Affects Versions: 1.24.0
> Reporter: Vladimir Sitnikov
> Assignee: Vladimir Sitnikov
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
