I think, machine strength has a part to play , but assuming there are some services or task that can be skipped when running while running (I mean running only) like compiling is fine every time but some components could be skipped plus there are many things at run time which could be probably load later like lazy loading or etc.
On Thu, Aug 27, 2020 at 4:33 PM Petri Tuomola <[email protected]> wrote: > Hi - do you mean building, or starting, or both? > > On my i7, I can do a full build (./gradlew clean bootRun) in 2 minutes - > which I don’t think is too bad. > > What I do find strange is that even if you don’t change anything, Gradle > seems to want to recompile everything - so even a rebuild takes about the > same amount of time. I was going to investigate why, but haven’t had a > chance yet. > > Regards > Petri > > > On 27 Aug 2020, at 12:23 PM, Saransh Sharma <[email protected]> wrote: > > Boot Run in development mode on an i5 based machine takes about 5 min. > (Does anyone have the same experience ) > > Possible to reduce the bootTime ? > > Maybe using thinBoot? > > Any thoughts? > > -- > Thanks and regards, > > Saransh Sharma > Research Partner > > This mail is governed by Muellners® IT policy. > The information contained in this e-mail and any accompanying documents > may contain information that is confidential or otherwise protected from > disclosure. If you are not the intended recipient of this message, or if > this message has been addressed to you in error, please immediately alert > the sender by reply e-mail and then delete this message, including any > attachments. Any dissemination, distribution or other use of the contents > of this message by anyone other than the intended recipient is strictly > prohibited. All messages sent to and from this e-mail address may be > monitored as permitted by applicable law and regulations to ensure > compliance with our internal policies and to protect our business. E-mails > are not secure and cannot be guaranteed to be error free as they can be > intercepted, amended, lost or destroyed, or contain viruses. You are deemed > to have accepted these risks if you communicate with us by e-mail. > > > -- Thanks and regards, Saransh Sharma Research Partner This mail is governed by Muellners® IT policy. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
