Re: Intellij build/test times
> I don't see why in the gradle.properties template we've messed with > the default daemon; this should purely be a personal choice and not > one where we the project need to make a strong preference for you. > I think the choice is still there - we generate this file with some sane defaults so that people can (and should!) modify it to their liking. The reason for the daemon timeout set to 15 mins is that if you're switching branches or play with jvm settings (different jvms), you'll quickly run out of memory (multiple gradle daemons running in the background). Dawid
Re: Intellij build/test times
I'm coming to this late but want to chime in to concur with most of Dawid's responses. I don't see why in the gradle.properties template we've messed with the default daemon; this should purely be a personal choice and not one where we the project need to make a strong preference for you. On Thu, Jun 13, 2024 at 9:43 PM Dawid Weiss wrote: > > > I would love to do that but it's almost like the three body problem - IDEs, > gradle and code changes. > > Dawid > > On Thu, Jun 13, 2024 at 8:49 PM Michael Sokolov wrote: >> >> Thanks for digging into this Dawid - I think it's important to keep an >> IDE dev path pretty clear of underbrush in order to encourage new >> joiners, even if it is not the primary or best means of building and >> testing >> >> On Thu, Jun 13, 2024 at 2:01 PM Dawid Weiss wrote: >> > >> > >> > Hi Mike, >> > >> > Just FYI - I confirm something is odd with the configuration evaluation. >> > The times vary wildly on my machine. I don't know why it's the case and I >> > couldn't pinpoint a clear cause. Once the daemon is running, things are >> > faster - perhaps you should increase the default daemon timeout (it also >> > applies to the IDE, I think): >> > >> > # timeout after 15 mins of inactivity. >> > org.gradle.daemon.idletimeout=90 >> > >> > I'll try to improve things by refreshing some of the build scripts. I >> > really liked gradle when it started - mostly for its simplicity. I don't >> > like how it turned from a build system to a distributed cache of prebuilt >> > artefacts... eh. >> > >> > Dawid >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Intellij build/test times
I would love to do that but it's almost like the three body problem - IDEs, gradle and code changes. Dawid On Thu, Jun 13, 2024 at 8:49 PM Michael Sokolov wrote: > Thanks for digging into this Dawid - I think it's important to keep an > IDE dev path pretty clear of underbrush in order to encourage new > joiners, even if it is not the primary or best means of building and > testing > > On Thu, Jun 13, 2024 at 2:01 PM Dawid Weiss wrote: > > > > > > Hi Mike, > > > > Just FYI - I confirm something is odd with the configuration evaluation. > The times vary wildly on my machine. I don't know why it's the case and I > couldn't pinpoint a clear cause. Once the daemon is running, things are > faster - perhaps you should increase the default daemon timeout (it also > applies to the IDE, I think): > > > > # timeout after 15 mins of inactivity. > > org.gradle.daemon.idletimeout=90 > > > > I'll try to improve things by refreshing some of the build scripts. I > really liked gradle when it started - mostly for its simplicity. I don't > like how it turned from a build system to a distributed cache of prebuilt > artefacts... eh. > > > > Dawid > > - > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
Re: Intellij build/test times
Thanks for digging into this Dawid - I think it's important to keep an IDE dev path pretty clear of underbrush in order to encourage new joiners, even if it is not the primary or best means of building and testing On Thu, Jun 13, 2024 at 2:01 PM Dawid Weiss wrote: > > > Hi Mike, > > Just FYI - I confirm something is odd with the configuration evaluation. The > times vary wildly on my machine. I don't know why it's the case and I > couldn't pinpoint a clear cause. Once the daemon is running, things are > faster - perhaps you should increase the default daemon timeout (it also > applies to the IDE, I think): > > # timeout after 15 mins of inactivity. > org.gradle.daemon.idletimeout=90 > > I'll try to improve things by refreshing some of the build scripts. I really > liked gradle when it started - mostly for its simplicity. I don't like how it > turned from a build system to a distributed cache of prebuilt artefacts... eh. > > Dawid - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Intellij build/test times
Hi Mike, Just FYI - I confirm something is odd with the configuration evaluation. The times vary wildly on my machine. I don't know why it's the case and I couldn't pinpoint a clear cause. Once the daemon is running, things are faster - perhaps you should increase the default daemon timeout (it also applies to the IDE, I think): # timeout after 15 mins of inactivity. org.gradle.daemon.idletimeout=90 I'll try to improve things by refreshing some of the build scripts. I really liked gradle when it started - mostly for its simplicity. I don't like how it turned from a build system to a distributed cache of prebuilt artefacts... eh. Dawid
