RubyMine takes a long time to launch - rubymine

All of a sudden my RubyMine IDE takes ~1 minute to launch the loading screen. This started happening right after I installed RubyMine and inserted the license. The IDE itself isn't slow, and file loading loads very fast too. How do I fix this?

Related

[java][eclipse] UI becomes unresponsive

I'm a seasoned software engineer and have used eclipse for well over 10 years. In the last week, Eclipse has decided to rebel against me. I'm dumbfounded.
Problem: I'm getting periods of very long UI unresponsiveness - on the order of 3 to 10 seconds. Generally, I'll be typing when the UI just stops writing text. It can vary from displaying spinning circle to not rendering anything in the window. Workspace building also slows down significantly.
I'm pulling my hair out trying to get tasks done! Any help appreciated.
Details:
It appears to start 10 minutes or more after starting eclipse. If I restart, it'll be ok for a few minutes.
This can happen in during any text entry. Though it's especially bad on code completion cases (i.e. "dot, cmd+space). Eclipse can also become unresponsive during anything else (moving the cursor, changing tabs, scrolling, etc).
CPU is not maxed out, though it appears CPU is pretty consistently at or over 50% - so maybe eclipse as pegged one thread/core?
Things I've Tried:
Updated from Neon.3 to Oyxgen.2. Deleted all projects from workspace and reimported. Upgraded memory in ini to -Xms512m -Xmx4000m -XX:PermSize=256m
-XX:MaxPermSize=512m. Deleted some metadata from a eclipse resource dir (don't recall which). Updated Java. No change. Haven't tried uninstalling all eclipse and reinstalling yet.
Setup:
Windows 10 Home (up-to-date), 12GB RAM, 64 bit, Oxygen.2 (4.7.2)
How large is your project? Do you build using Eclipse, or do you build externally?
If you notice a progress bar in the lower right side of the GUI during these periods of unresponsiveness, it's likely Eclipse's Build Automatically feature causing your issue. If so, it can be disabled under Project -> Build Automatically.

Eclipse Neon Pathetically Slow

Is there a way to identify what's going on with Eclipse when a file is saved?
My eclipse runs extremely slow (takes close to 3 minutes to save a file). Simple addition of a space in a file and save, it keeps saying 'Updating Navigator Content Viewer' and 'Remote System Explorer Operation' and simply freezes.
I am running on a powerful system with 16 gigs of ram and assigned 1 gig for eclipse. The way it performs is simple unacceptable and planning to switch all my projects to NetBeans rather than wasting hours on save.
Any hints on fixing this are appreciated.
Finally resolved the issue by getting rid of Eclipse.
Moved all my projects to NetBeans 8.2. Its a big relief to see my projects getting saved in a split second.
Coming to Eclipse, it is powerful and exceptional on all aspects other than the slowness during save. However, this frustrating issue alone makes me rate Eclipse 1 (may be 0) on a scale of 10. Cannot expect a developer to wait for 2 minutes to save a file (on a 16 gig system, with 4 gigs assigned to Eclipse) which would drag the productivity drastically.
Looks like this issue is not something new as I have seen many posts on various forums regarding the same. I don't understand how Eclipse never gave a thought on this slowness issue.
First you should try to look at this post so:
Check if it is the latest version (I personally run Neon 4.6 and it takes about 2 minutes to parse and save a 55MB file)
Check your JDK/JRE
You should also try to see if it doesn't come from your drive...
If you still have the problem, I suggest you look at the other Eclipse versions (Mars...)

SCALA-IDE: Eclipse highlight matching variables / mark occurrences extremely slow

I just installed the SCALA-IDE plugin and the highlighting in it is excruciatingly slow (circa 1 minute on a 1k-line file) rendering it useless. Meanwhile, the same Eclipse session with the PyDev plugin still works within about a second on very large files.
I was wondering if there was a way to speed it up?

Apache Spark running slower when IntelliJ not in focus

I am running Apache Spark in IntelliJ, using the console to send requests to my application.
I have noticed something I find quite strange. On my Mac, when running my program and having IntelliJ as the selected window i.e. full screen and visible; I get through 1000 iterations in ~5 minutes. When I start the application in IntelliJ and then make the visible screen another application, but do nothing with it - literally just leave the Mac alone, when I go back to the Scala Console after ~5 minutes it has only performed 300 iterations! Similarly, if the app starts and then the screens turns off (but my Mac doesn't sleep - I made sure of that) I get the same issue: only 300 iterations.
Is there any explanation for this?

Launching a Project in Eclipse

I am trying to run my projects in Eclipse, whenever I used to run any program a window appear and it shows that project is launching and building.
This never happened before. In fact, it was working very okay an hour before but now, even for old created project it showing this and not moving ahead.
Is this a general thing happened in eclipse as I haven't seen this before.
I want to get out of this to move ahead and to run the project.
The Launcher looks like this :
The progress Bar is also not moving ahead if it's building the project.
It's definitely normal to see; there's times I'll see it two or three times in a day. It shows up if the launching process is waiting on anything or is expected to take more than a couple seconds.
In your case, it seems to be stuck on "Building workspace," which happens when you open Eclipse. The more projects you have in Eclipse and the more sections of workspace you have (groups of tabs), the longer it takes to build your workspace. So I'm going to wager a guess that you tried to launch a project within the first minute or two of Eclipse being open. Am I right?
If that's the case, just wait a bit, and watch the lower right corner (where it says "Launching Clock" in your screenshot). When it shows it's stopped trying to do start-up tasks, you should be good to go.
If Eclsipse had been open for a while, then perhaps Eclipse is busy with other junk and calling it "Building workspace." Maybe it's having a hard time understanding what to do with one of your projects, so check for compiler errors. You can also try to "clean" your projects (Project -> Clean).
If that also fails...hmmm...I'm sure there's other options before you get to this point, but you might need to re-install Eclipse. I suppose there's a chance that in the deep dark corners of Eclipse, a file was corrupted, causing Eclipse to hang on a task that requires a missing/bad file. But before you go this far, make you get second or third opinions, because I might be missing some simpler cause of your Eclipse hanging than what I've listed already.
I found the solution.
I don't know what was the error and why it was displaying the Launcher window and stuck there. But, I forcefully stopped eclipse using Task Manager and then restarted it.
When restarted it took few minutes (more than usual time) and I was done with it. now it's working okay.
Re-installation of Eclipse also worked but i tried this before re-installing or upgrading.