Please confirm...
-
Would it be possible to suggest next name for Ubuntu OS ? How is "Molasses" ?? Seriously - is OS multitasking thing of the past ? System monitor shows about 20% of usage on each of four CPU, and about the same amount of memeory in use... What makes the CPU to run 100% or more ? Assembly language ??
-
Would it be possible to suggest next name for Ubuntu OS ? How is "Molasses" ?? Seriously - is OS multitasking thing of the past ? System monitor shows about 20% of usage on each of four CPU, and about the same amount of memeory in use... What makes the CPU to run 100% or more ? Assembly language ??
Suggest away! :) But you know what they say! In space no one can hear your suggestions! (Or something...)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Would it be possible to suggest next name for Ubuntu OS ? How is "Molasses" ?? Seriously - is OS multitasking thing of the past ? System monitor shows about 20% of usage on each of four CPU, and about the same amount of memeory in use... What makes the CPU to run 100% or more ? Assembly language ??
-
Would it be possible to suggest next name for Ubuntu OS ? How is "Molasses" ?? Seriously - is OS multitasking thing of the past ? System monitor shows about 20% of usage on each of four CPU, and about the same amount of memeory in use... What makes the CPU to run 100% or more ? Assembly language ??
Ubuntu now using VB6 for source. Use Debian.
>64 Some days the dragon wins. Suck it up.
-
Ubuntu now using VB6 for source. Use Debian.
>64 Some days the dragon wins. Suck it up.
-
Would it be possible to suggest next name for Ubuntu OS ? How is "Molasses" ?? Seriously - is OS multitasking thing of the past ? System monitor shows about 20% of usage on each of four CPU, and about the same amount of memeory in use... What makes the CPU to run 100% or more ? Assembly language ??
You'll have to get rid of any I/O if you want 100% CPU.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
Would it be possible to suggest next name for Ubuntu OS ? How is "Molasses" ?? Seriously - is OS multitasking thing of the past ? System monitor shows about 20% of usage on each of four CPU, and about the same amount of memeory in use... What makes the CPU to run 100% or more ? Assembly language ??
Member 14968771 wrote:
What makes the CPU to run 100% or more ? Assembly language ??
Ultimately, yes, sorta, kinda, maybe, in that everything *eventually* gets down to machine code. Even things running in a JVM or CLI environment have to, at some point, run on the host CPU. But that's a lot of overhead, especially if you're seeing it constantly. I'm looking at my Ubuntu 21.10 VmWare instance with 2 CPU and 2 G of ram and top shows 99.7 % idle. I am using about 1.0 G of ram, but 600MB of that is buffered/cache so it's essentially available for program use. That's with the system otherwise idle - only a single GUI login and a terminal running top. What tools are you using to get your CPU usage? Maybe take a look at atop or glances, both of which provide more detail than top or htop.
Keep Calm and Carry On
-
theoldfool wrote:
Ubuntu now using VB6 for source. Use Debian.
I understand the joke you were making, but...Ubuntu is based on Debian.
True, Ubuntu took Debian and "improved it", I think Microsoft helped them. I rest my case. :)
>64 Some days the dragon wins. Suck it up.
-
Member 14968771 wrote:
What makes the CPU to run 100% or more ? Assembly language ??
Ultimately, yes, sorta, kinda, maybe, in that everything *eventually* gets down to machine code. Even things running in a JVM or CLI environment have to, at some point, run on the host CPU. But that's a lot of overhead, especially if you're seeing it constantly. I'm looking at my Ubuntu 21.10 VmWare instance with 2 CPU and 2 G of ram and top shows 99.7 % idle. I am using about 1.0 G of ram, but 600MB of that is buffered/cache so it's essentially available for program use. That's with the system otherwise idle - only a single GUI login and a terminal running top. What tools are you using to get your CPU usage? Maybe take a look at atop or glances, both of which provide more detail than top or htop.
Keep Calm and Carry On
I am not going to spent much time analyzing the molasses. I am a user and past few "releases" have been getting steadily slower. Doing any more detailed technical analysis would be pointless. My primary usage is hobby C code - but when I keep getting " such and such application is not responding Wait ... " or "file corruption , run fsck manually..." I am going to start a different hobby...
-
Member 14968771 wrote:
is OS multitasking thing of the past ?
No, but it does require you to write efficient multitasking code. Yet another subject for you to apply your energies towards learning.
I had my education in the ages when 'timesharing' was something new. Our textbooks tried to make us believe that it let you behave as if you had an entire machine to ourselves. All us IT students insisted that timesharing was what made you realize that you did not have the machine to yourself.
-
Would it be possible to suggest next name for Ubuntu OS ? How is "Molasses" ?? Seriously - is OS multitasking thing of the past ? System monitor shows about 20% of usage on each of four CPU, and about the same amount of memeory in use... What makes the CPU to run 100% or more ? Assembly language ??
Your code may, directly or indirectly, require access to some common resource that is, for synchronization purposes, locked by some other process, so you have to wait for that other process to release it. It is not uncommon that processes hold onto their resources for a long time. Ages ago, I was working on an OS (not "*nix-like") that for any write operation required the process to reserve the file system root, i.e. the entire file system. Only a single file write could be active at any one time (!). In database systems, you frequently see programs locking entire tables (or even the entire database!) while they are doing all their processing, which may take a long time. Some database systems doesn't give you any other option than locking tables, so software ported from systems offering tuple/predicate locking may cause terrible performance with other database systems (until applications are rewritten to do their work without keeping tables locked). Obviously, the same goes for other system resources. Some software put locks on I/O devices, system data structures (note: 'system' doesn't necessarily mean 'operating system'!) etc. far beyond the actual time they need it. You may empathize with these developers, "sort of". Only sort of. It is convenient reserving everything you need beforehand, so that you can be sure it is all available, perform all your operations on all your resources, and then release everything. First, you keep your operations code free of any resource management code. Second, you are relieved of the analysis job of determining when you really need the different resources. Third: You avoid the problem of getting halfway in your work, and then having to handle the situation that you have to wait for some resource to become available. There are lots of code out there that is rather 'uneconomical' in their occupation of common resources. I do suspect that other applications, utilities, demons, servers, whatever ... more commonly is to blame than the OS. If you are competing with others for shared resources, you will have the same competition even if you code in assembler. A purely CPU-consuming application will run at full speed. However, what you believe is a 'purely CPU-consuming application' may at closer inspection turn out to not be.
-
I am not going to spent much time analyzing the molasses. I am a user and past few "releases" have been getting steadily slower. Doing any more detailed technical analysis would be pointless. My primary usage is hobby C code - but when I keep getting " such and such application is not responding Wait ... " or "file corruption , run fsck manually..." I am going to start a different hobby...
-
True, Ubuntu took Debian and "improved it", I think Microsoft helped them. I rest my case. :)
>64 Some days the dragon wins. Suck it up.
-
Your code may, directly or indirectly, require access to some common resource that is, for synchronization purposes, locked by some other process, so you have to wait for that other process to release it. It is not uncommon that processes hold onto their resources for a long time. Ages ago, I was working on an OS (not "*nix-like") that for any write operation required the process to reserve the file system root, i.e. the entire file system. Only a single file write could be active at any one time (!). In database systems, you frequently see programs locking entire tables (or even the entire database!) while they are doing all their processing, which may take a long time. Some database systems doesn't give you any other option than locking tables, so software ported from systems offering tuple/predicate locking may cause terrible performance with other database systems (until applications are rewritten to do their work without keeping tables locked). Obviously, the same goes for other system resources. Some software put locks on I/O devices, system data structures (note: 'system' doesn't necessarily mean 'operating system'!) etc. far beyond the actual time they need it. You may empathize with these developers, "sort of". Only sort of. It is convenient reserving everything you need beforehand, so that you can be sure it is all available, perform all your operations on all your resources, and then release everything. First, you keep your operations code free of any resource management code. Second, you are relieved of the analysis job of determining when you really need the different resources. Third: You avoid the problem of getting halfway in your work, and then having to handle the situation that you have to wait for some resource to become available. There are lots of code out there that is rather 'uneconomical' in their occupation of common resources. I do suspect that other applications, utilities, demons, servers, whatever ... more commonly is to blame than the OS. If you are competing with others for shared resources, you will have the same competition even if you code in assembler. A purely CPU-consuming application will run at full speed. However, what you believe is a 'purely CPU-consuming application' may at closer inspection turn out to not be.
I really did not intended to start deep technical discussion about the "molasses" OS , but... Explain this to me - I do not recall which "release " started this - but every now and then I am getting " application xyz is not responding " and the options are "quit it" or "wait". And it does not matter what app is "not responding". For instance ,when I do "software update" - with nothing else running - I get this stupid dialog right away... I may have very simplistic view on things - but when this started with OS version X it cannot be because it is Friday .... or some other process is using common resources...