IntelliJ IDEA 2020.1 EAP is open • Hacker News Board

Re: IntelliJ IDEA 2020.1 EAP is open

#41

Post by kjeetgill » Sat, Jan 25, 2020, 1:34 PM UTC

soulnothing wrote: post #25

One of the things I find interesting here is the SQL support via JaSync. A competitor to JDBC using netty and kotlin coroutines, or on Java Completable Futures.. https://github.com/jasync-sql/jasync-sql Spring R2DBC and Vertx are built atop that library. I'm also working on a micro orm using it. But it's really nice to see that become a first class citizen in the IDE.

Nitpick: I think it's J-Async not JaSync. As in an asynchronous SQL implementation.

For anyone else wondering, I believe it targets just MySQL and Postgres.

Re: IntelliJ IDEA 2020.1 EAP is open

#42

Post by Mattwmaster58 » Mon, Jan 27, 2020, 11:43 PM UTC

namibj wrote: post #10

ctas wrote: post #3

Really excited about the speed improvements they promised for this version. Even on a machine with 16GB RAM and increased max. memory for the JVM the UI just feels too slow.

Easy fix: replace the the existing GC line with -XX:+UnlockExperimentalVMOptions -XX:+UseZGC and enjoy no more visible lag spikes.

Do you mean for recent, IntelliJ based IDEs? Interestingly, when I tried this with Pycharm Pro 2019.3.2 I got: ``` Error occurred during initialization of VM Option -XX:+UseZGC not supported ```

Re: IntelliJ IDEA 2020.1 EAP is open

#43

Post by namibj » Thu, Jan 30, 2020, 12:40 AM UTC

Mattwmaster58 wrote: post #42

namibj wrote: post #10

Earlier quoted context omitted.

Easy fix: replace the the existing GC line with -XX:+UnlockExperimentalVMOptions -XX:+UseZGC and enjoy no more visible lag spikes.

Do you mean for recent, IntelliJ based IDEs? Interestingly, when I tried this with Pycharm Pro 2019.3.2 I got: ``` Error occurred during initialization of VM Option -XX:+UseZGC not supported ```

You need a newer JVM. It needs to be at least Java 11.

Re: IntelliJ IDEA 2020.1 EAP is open

#44

Post by namibj » Thu, Jan 30, 2020, 2:09 PM UTC

yole wrote: post #13

namibj wrote: post #10

Earlier quoted context omitted.

Easy fix: replace the the existing GC line with -XX:+UnlockExperimentalVMOptions -XX:+UseZGC and enjoy no more visible lag spikes.

If it was this easy, we'd have enabled this by default. Unfortunately by far not all UI freezes in IntelliJ IDEA are caused by GC, and ZGC is not a wholesale performance improvement even for those scenarios which do depend on GC.

Not all, but with the default settings I had freezes, even if I had more than 300% over provisioning. The requirement is "no GC pauses that cause frame drops" (well, occasional single-frame drops aren't really noticeable, but anything worse starts to become visible).

A large issue is afaik the lack of memory reclamation and the over provisioning required to even really work at all.