Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » U++ community news and announcements » 2022.3rc1
Re: 2022.3rc1 [message #59393 is a reply to message #59384] Tue, 20 December 2022 11:10 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13980
Registered: November 2005
Ultimate Member
coolman wrote on Mon, 19 December 2022 19:25
mirek wrote on Mon, 19 December 2022 18:22
coolman wrote on Mon, 19 December 2022 17:31
mirek wrote on Mon, 19 December 2022 11:47
coolman wrote on Mon, 19 December 2022 10:32
mirek wrote on Mon, 19 December 2022 09:34
coolman wrote on Mon, 19 December 2022 07:47
Hi Mirek,

I've been testing latest version master version from the GitHub and I really don't like the behaviour of the IDE when editing the file.
- I mean the cursor getting stuck while typing, when the delay between pressing a key and then writing a character is too long.
- Also, double clicking on a word to highlight the word does not work properly. I have to try double clicking multiple times with different speeds to get this feature to work at all.

OS: Ubuntu 20.04
Linux 5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22 21:24:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Ubuntu clang version 13.0.1-++20220120110924+75e33f71c2da-1~exp1~20220120231001.5 8


Is this specific for the latest version? (If not, why are your reporting this now ? Smile

I started regularly using the latest version of the IDE after the Alt+J fix.

Quote:

Does switching off Assist help?

Yes it can help.

Quote:

What is your CPU?

cat /proc/cpuinfo
vendor_id : GenuineIntel
cpu family : 6
model : 165
model name : Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz
stepping : 2
microcode : 0xf0
cpu MHz : 2700.000
cache size : 12288 KB
physical id : 0
siblings : 12
...

BR, Radek


This is probably Assist indexer overloading your HW. Please try to reduce the number of indexer threads (Setup/Settings/Assist/Number of indexer threads).

Also report what default number do you have there. IMO it should be 10, if there is more, maybe you have tested some time ago and it was left with much higher number.

(Default settings are in ClangConfigSetDefaults, currently I set indexer threads at CPU threads - 2). Maybe this need finetuning.


10 indexing threads were set up.
I tried reduce the number of indexer threads but after a while, the behaviour described above returned again. I monitored the running of the IDE using htop and noticed that occasionally a thread consumed more percent of the processor it was assigned to when I was typing. When I tried to double-click, the main IDE thread was consuming up to 18 percent of CPU and still the word was not highlighted.

What confuses me is that I can see a lot of threads assigned to the main process. And the number of threads is equal to 2x the number of CPU cores. The current output from pstree is when 4 of indexing threads was set. But it doesn't matter how many indexing threads is set up, the output is still the same.
pstree -tpch 121637
ide(121637)─┬─{dconf worker}(121639)
            ├─{gdbus}(121640)
            ├─{gmain}(121638)
            ├─{ide}(121642)
            ├─{ide}(121643)
            ├─{ide}(121644)
            ├─{ide}(121645)
            ├─{ide}(121646)
            ├─{ide}(121647)
            ├─{ide}(121648)
            ├─{ide}(121649)
            ├─{ide}(121650)
            ├─{ide}(121651)
            ├─{ide}(121652)
            ├─{ide}(121653)
            ├─{ide}(121654)
            ├─{ide}(121655)
            ├─{ide}(121736)
            ├─{ide}(121737)
            ├─{ide}(121738)
            ├─{ide}(121739)
            ├─{ide}(121740)
            ├─{ide}(121784)
            └─{threaded-ml}(121666)



Edited:
While editing I noticed that a single thread can use up to 60% of the dedicated CPU while the main thread uses up to 80% of the allocated CPU.


What if you switch assist off completely? (Just to find out where to look next, is that Assist related or not...) (Do not forget to restart theide)

(Those threads are fine - those are CoWork worker threads, there should be 14 of them. Most of time they are just waiting).

Mirek


When asssist is turned off, the problems do not appear. And the main thread consumes around 20% of CPU.

Radek


What about leaving Assist on and disabling "Indexer gets invoked automatically" (and restarting).

Also, is it a problem even with 1 indexer thread?

How much RAM do you have?

(For reference, I am testing with 2400G (4C/8T) with 8GB RAM, Ubuntu 20.04. Assist feels slower than my Win machine (5950x), but no symptoms as you describe. So I am puzzled).
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Merry Christmas and Happy New Year 2023!
Next Topic: 2022.3
Goto Forum:
  


Current Time: Wed May 22 21:10:51 CEST 2024

Total time taken to generate the page: 0.01573 seconds