I came to this forum to report the very same issue. I definitely disagree with the statement that hanging is normal for any software, Java software included. The issue with Java software tends to be that it is often times an Enterprise software. Enterprise software tends to be done for deadlines, not quality. Due to historic reasons the Java tends to be the technology for creating Enterprise software, which might explain the impression that all Java software is of low quality and has problems. Another aspect with anything with the word “Enterprise” in it is that unlike freelancers and home users and small businesses, the Enterprises have a lot of money to waste and fast delivery is more important than efficient use of money. Optimized, efficient, software takes longer to develop, so it makes sense to leave things unoptimized and just buy a lot of hardware that has a lot of CPU-power and RAM. That may also explain the typical “good” software development practice of first writing really low quality, crappy, software and then later trying to gradually turn shit into gold by trying to rewrite parts of software with dirty-hackish-flawed-architecture and then hope to fix the speed and RAM and other resource consumption issues like that, in stead of taking far longer to deliver the very first version, but then deliver a version that is reasonably optimized from the very start. Well, Enterprises have a lot of money to burn and the software companies that do that kind of contract work certainly do not complain about a situation, where a client is offering a lot of money for an additional project.
I find the YaCy project to be a very inspirational and from functionality point of view a step in the right direction. However, my observations are that the GUI problems seem to start after the YaCy instance has indexed some pages and the GUI problems seem to not occur, if the YaCy instance Java VM has a lot of RAM allocated to it. In my case, 600MiB of JVM allocated RAM will run without the GUI, but about 1.2GiB will kind of work. I also noticed that the original authors of the YaCy project seem to run a consultancy business, where they use the YaCy as their core technology. That may explain, why they might not test the YaCy with lower RAM consumption scenarios. After all, businesses have the money to just buy computers with a lot of RAM and speed and comfort has higher priority than RAM consumption. Unfortunately the business use case differs substantially from the hactivist use case. In my opinion it is perfectly OK for a P2P-search engine to crawl with the speed of 1 HTML-page per 5s or even 10s and have a ~5GiB index on an USB-stick that is connected to a 1-core, 700MHz Raspberry_Pi with 512MiB of RAM and an USB storage read/write speed of about 1MB/s. It seems to me that the YaCy is totally unoptimized for that kind of a use case.
I remember that one of texts at the YaCy command line console kindly asked for feedback, how the YaCy could be updated to make it fit better with the end user use case. I’m not sure that it makes sense to start re-writing the current YaCy implementation, but it certainly makes a lot of sense to CREATE AN API THAT CAN BE USED BY OTHER P2P-search-engines so that different P2P-search engines can use the same P2P-seach-engine-network and YaCy could also use the indexes of those other P2P-search-engines.
The idea of defining a common P2P-interface for different P2P-software projects is not new. For example, there are multiple BitTorrent clients that all use the same protocol and therefore can exchange files, despite being written in different programming languages. A concrete example is also the Fediverse of P2P-social network software, where different P2P-social-network applications support multiple P2P-social-networking-protocols and form a common, huge, network. The details of that might be found from
So, all in all, I think that the YaCy is IDEOLOGICALLY a very nice project, but its implementation is absolutely ill-suited for non-enterprise use cases. But, it’s a nice first step and if it is possible to agree on a P2P-protocol, then things can start moving
Thank You for reading my comment.