(Solved) systemd-journald extremely high CPU usage

I started noticing this problem a few days ago, but I thought it was because I was running too much with too little RAM. But when running nothing more than a KDE desktop, my CPU usage bounces between 50% and 100%, making things laggy. It looks like systemd-journald is to blame, as it is using 50% of the CPU. This is an AMD Phenom II dual core, so this definitely shouldn't be happening. I noticed journal logs were more than 2 GB, so I deleted everything within /var/log/journal/. Rebooted, no change, so I disabled journal storage, but that did not solve the problem.
Nothing in the logs looks like a problem to me:
$ sudo journalctl
-- Logs begin at Tue 2013-03-12 17:31:37 PDT, end at Tue 2013-03-12 18:15:56 PDT. --
Mar 12 17:31:37 silverstone systemd-journal[149]: Allowing runtime journal files to grow to 298.6M.
Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpuset
Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpu
Mar 12 17:31:37 silverstone kernel: Linux version 3.7.10-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (G
Mar 12 17:31:37 silverstone kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=31669ea0-76db
Mar 12 17:31:37 silverstone kernel: e820: BIOS-provided physical RAM map:
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cff8ffff] usable
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff90000-0x00000000cff9dfff] ACPI data
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff9e000-0x00000000cffdffff] ACPI NVS
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cffe0000-0x00000000cfffffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001afffffff] usable
Mar 12 17:31:37 silverstone kernel: NX (Execute Disable) protection: active
Mar 12 17:31:37 silverstone kernel: SMBIOS 2.5 present.
Mar 12 17:31:37 silverstone kernel: DMI: MSI MS-7642/890GXM-G65 (MS-7642) , BIOS V1.2 03/31/2010
Mar 12 17:31:37 silverstone kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
Mar 12 17:31:37 silverstone kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 12 17:31:37 silverstone kernel: No AGP bridge found
Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0x1b0000 max_arch_pfn = 0x400000000
Mar 12 17:31:37 silverstone kernel: MTRR default type: uncachable
Mar 12 17:31:37 silverstone kernel: MTRR fixed ranges enabled:
Mar 12 17:31:37 silverstone kernel: 00000-9FFFF write-back
Mar 12 17:31:37 silverstone kernel: A0000-EFFFF uncachable
Mar 12 17:31:37 silverstone kernel: F0000-FFFFF write-protect
Mar 12 17:31:37 silverstone kernel: MTRR variable ranges enabled:
Mar 12 17:31:37 silverstone kernel: 0 base 000000000000 mask FFFF80000000 write-back
Mar 12 17:31:37 silverstone kernel: 1 base 000080000000 mask FFFFC0000000 write-back
Mar 12 17:31:37 silverstone kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
Mar 12 17:31:37 silverstone kernel: 3 disabled
Mar 12 17:31:37 silverstone kernel: 4 disabled
Mar 12 17:31:37 silverstone kernel: 5 disabled
Mar 12 17:31:37 silverstone kernel: 6 disabled
Mar 12 17:31:37 silverstone kernel: 7 disabled
Mar 12 17:31:37 silverstone kernel: TOM2: 00000001b0000000 aka 6912M
Mar 12 17:31:37 silverstone kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Mar 12 17:31:37 silverstone kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0xcff90 max_arch_pfn = 0x400000000
Mar 12 17:31:37 silverstone kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff880
Mar 12 17:31:37 silverstone kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
Mar 12 17:31:37 silverstone kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
$ systemctl status systemd-journald
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Tue 2013-03-12 18:10:41 PDT; 8min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 142 (systemd-journal)
Status: "Processing requests..."
CGroup: name=systemd:/system/systemd-journald.service
`-142 /usr/lib/systemd/systemd-journald
However, it looks like the log files keep getting corrupted:
$ sudo journalctl --verify
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000007f543-0004d7c4445effa4.journal
Invalid object contents at 124687944ââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal:124687944 (of 134074368, 92%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal (Bad message)
Invalid object contents at 75715936âââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal:75715936 (of 76156928, 99%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal (Bad message)
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000290d6-0004d7c3a0033472.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000000001-0004d7c413227650.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000fcfc0-0004d7c3fd8ee9c5.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
Invalid object contents at 124701856ââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal:124701856 (of 134049792, 93%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal (Bad message)
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-00000000000a9da8-0004d7c45187e39e.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000d26b1-0004d7c3ea1b73f7.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000002a43f-0004d7c425785944.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000539fb-0004d7c3b2d1f935.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000054d23-0004d7c4354da4ef.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@2c1af599e637441985385fe37ded2a2c-0000000000001706-0004d7c38cd3de88.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@5e6edd359123491f9998a310206ccbf9-00000000000019b4-0004d7c4153f8628.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-000000000007e345-0004d7c3c3ed8197.journal
I am using a two or three year old SSD, so maybe it has gotten some bad sectors? But that doesn't explain why journald still bricks things when it isn't logging anything. The install is 10 months old, and I switched from init to systemd around October. Is there anything I can do, short of reinstalling?
Thanks,
Nicholas
Last edited by bicyclingrevolution (2013-03-14 05:57:13)

Thanks for the tip ilkyest, but it didn't make any difference to the systemd-journald problem.
However, I looked at journalctl again and found it cluttered with CUPS failures:
-- Logs begin at Tue 2013-03-12 19:17:00 PDT, end at Wed 2013-03-13 22:31:31 PDT. --
Mar 12 19:17:00 silverstone spideroak_inotify[796]: Program started
Mar 12 19:21:30 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 7199 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5471 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5699 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-coredump[1592]: Process 1590 (cupsd) dumped core.
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-RGB..
Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_3840
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-RGB..
Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_F4100
Mar 12 19:21:28 silverstone dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mar 12 19:21:28 silverstone dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs
Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-RGB..
Mar 12 19:21:28 silverstone colord[354]: device removed: cups-Deskjet_3840
Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-Gray..
Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-RGB..
Mar 12 19:21:31 silverstone colord[354]: device removed: cups-Deskjet_F4100
Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or director
Mar 12 19:21:31 silverstone systemd-journal[143]: Missed 6365 kernel messages
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone cupsd[1590]: Unknown directive DefaultAuthType on line 9.
Mar 12 19:21:31 silverstone cupsd[1590]: cupsd: client.c:757: avahi_client_get_host_name: Assertion `client' failed.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone cupsd[1594]: Unknown directive DefaultAuthType on line 9.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Disabling cups solved the CPU usage issue.
It looks like the root of the problem is Avahi failing to start, but I have no idea why it isn't working.
$ systemctl status dbus-org.freedesktop.Avahi.service
dbus-org.freedesktop.Avahi.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)

Similar Messages

Microsoft Office 2004 -- extremely high cpu usage and virtual ram

hi,
when i use office it causes a very high cpu usage even when its in idle mode.
i am unable to work with it, because its extremely slow.
does anyone have same experiences?
thanks for your help!
mbp 2.0 1,5gb ram 80gb hdd Mac OS X (10.4.7)

I am able to work OK with office, I'm using the 'old version' Microsoft Office v.X, not much details in the About Box, just listed as MSoft Word/Excel/etc for Mac service release 1.
I get the occasional crash, and I have seen Word in particular use 90% of a single core and amazingly large virtual memory usage, gigabytes sometimes, but eventually the document gets printed.
It shows how useful the dual core (or quad) cpu approach is!
One cpu for Word to print, and one cpu to run the rest of my applications/life!
I still use this old office rather than re-booting into Window§ for whatever is the latest version of office.
Doing some playing with a similar one page document in Office v.X and Pages 2.01, I get Word using about 25% of a core , Pages using 5%, - whilst editing; Intel native Pages has 20% of a core and 80MB ram 480 virtual whilst printing, Word has about 100% of a core and 65MB ram 650 virtual whilst printing, but it is a powerPC code so Rosetta is in there somewhere.
check Activity Monitor or other apps/widgets for some parasitic processes? have fun!
many Macs 512k -> MacBool Pro 2GHz 1GB ram Mac OS X (10.4.7) Yes, I have Key Lime

Lightroom Mobile Sync - Extremely High CPU Usage/Sync Process Causes LR To Lag

Since my other thread doesn't seem to be getting any responses, I'm pasting what I've found here. Please keep in mind I am not a beginner with Lightroom and consider myself very familiar with Lightroom's features excluding the new mobile sync.
1st message:
I'm on Lr 5.5 and using the 30 day trial of Adobe CC to try syncing one collection of slight more than 1000 images. Despite already having generated the Smart Previews, I can see my CPU crunching through image after image (the rolling hills pattern in the task manager) while doing the sync. I was assuming, since I already created the Smart Previews, that the sync of this collection would begin immediately and be done by simply uploading all of the existing Smart Previews. The Smart Previews folder of the catalog is 871MB and has stayed the same despite the CPU obviously doing *something*. As it is now, the sync progress is incredibly slow, almost at a pace like it's actually exporting full-res JPGs from the RAW images (as a comparison only, I know this should not be what it's actually doing).
Another side effect of this is that I'm basically unable to use my computer for other tasks due to the high CPU utilization.
Win 7 x64 / Lightroom 5.5
Intel i5 2500k OC'd 4.5GHz
16GB RAM
SSD for OS, separate SSD for working catalog and files
2nd message:
As a follow up, now Lightroom thinks all 1026 photos are synced (as shown in "All Sync Photographs" portion of the Catalog though all images after the 832nd image show the sync icon per image stuck at "Building Previews for Lightroom Mobile" and the status at the top left corner has been stuck at "Syncing 194 photos" for over 12 hours. Is there no option to force another sync via Lightroom Desktop and also force the iOS app to manually refresh (perhaps by pulling down on the collections view, like refreshing via the Mail app)?
3rd message:
One more update, I went into Preferences and deleted all mobile data, which automatically signed me out of Adobe CC and then I signed back in. Please keep in mind the Smart Previews were long generated before even starting the trial, and I also manually generated them again (it ran through quickly since it found they were already generated) many times. Now that I'm re-syncing my collection of 1026 images, I can clearly see Lightroom using the CPU to regenerate the Smart Previews which already exist. I have no idea why it's doing this except that it's making the process of uploading the Smart Previews extremely slow. I hope this time around it will at least sync all 1026 images to the cloud.
4th message:
All 1026 images synced just fine and I could run through my culling workflow on the iPad/iPhone perfectly. Now I'm on a new catalog (my current workflow unfortunately uses one catalog per event) and I see the same problem: Smart Previews already generated but when syncing, Lightroom seems to re-generate them again anyway (or take up a lot of CPU simply to upload the existing Smart Previews). Can anyone else chime in on what their CPU utilization is like during the sync process when Smart Previews are already created?
New information:
Now I'm editing a catalog of images that is synced to Lightroom Mobile and notice that my workflow has gotten even slower between photos (relative to what it was before, this is not a discussion about how fast/slow LR should perform). Obviously Lightroom is syncing the edited settings to the cloud, but I can see my CPU running intensively (all 4 cores) on every image I edit and the CPU utilization graph looks different than before I started using LR mobile sync. It still feels like every change isn't simply syncing an SQLite database change but re-generating a Smart Preview to go with it (I'm not saying this is definitely what's happening, but something is intensively using the CPU that wasn't prior to using LR Mobile).
For example: I only update the tint +5 on an image. I see the CPU spike up to around 30-40%, then falls back down, then back up to 100%, then back down to another smaller spike while Lightroom says "Syncing 1 photo". I've attached a screenshot of my CPU graph when doing this edit on just one image. During this entire time, if I try to move onto edit another image, the program is noticeably slower to respond than it was prior to using LR mobile, due to the fact that there appear to be much more CPU intensive tasks running to sync the previous edit. This is proven by un-syncing the collection and immediately the lag goes away.
I'd be happy to test/try anything you have in mind, because it's my understanding that re-syncing photos that are edited that are already in the cloud should be simply updating the database file rather than require regenerating any Smart Previews or other image data. If indeed that's what it should be doing, then some other portion of LR is causing massive CPU usage. If this continues, I will probably not choose to proceed with a subscription despite the fact that i think LR mobile adds a lot of value and boosts my workflow significantly if it wasn't causing the program to lag so badly in the process.
I know this message was incredibly long and probably tedious to read through so thanks in advance to anyone who gets through it
-Jeff

Thanks for reporting. Just passed along your info to some of our devs. One of the things that needs to be created (beside smart previews) during an initial sync are thumbnails + previews for the LrM app - Guido
Hi Guido,
Thanks for pointing this out. I realized the same thing when I tried syncing a collection for offline mode and found out the required space sounded more like Previews + Smart Previews rather than just the Smart Previews.
greule wrote:
Hi Jeff, are your images particularly large or do you make a lot of changes which you save to the original file as part of your workflow?
The CPU usage is almost certainly from us uploading JPEG previews not the Smart Previews - particularly during develop edits as these force new JPEG previews to be sent from Lightroom desktop, but would not force new Smart Previews (unless the develop edits are modifying the original file making us think the Smart Preview is out of date) to be sent.
Guido
My images are full-resolution ~22mp Canon 5D Mark III RAW files so they're fairly large. Even if I only make one basic change such as exposure changes, I saw the issue. By "save to the original file" I'm assuming metadata changes such as timestamps, otherwise edits to the images aren't actually written to the original file. I'm only doing develop module edits so I shouldn't be touching the original file at all at this point in my workflow.
I think it makes sense now that you mention that new JPEG previews need to be generated and sent to the cloud due to updated develop edits. My concern is that this seems to be done in real-time as opposed to how Lightroom Desktop works (which is to render a new Standard Preview or 1:1 Preview on demand, which means only one is being rendered at any given time while viewing it in Loupe View or possibly 2 in Compare View). If I edit, for example, 10 images quickly in a row, once the sync kicks in a few seconds later, editing the 11th image is severely hindered due to the previous 10 images' JPEG previews being rendered and sync'd to the cloud (I'm assuming the upload portion doesn't take much CPU, but the JPEG render will utilize CPU resources to the fullest if it can). Rendering Standard/1:1 Previews locally and being able to walk away while the process finishes works because it is at the start of my workflow, but having to deal with on-the-fly preview rendering while I'm editing greatly impacts my ability to edit. Perhaps there can be a way to limit max CPU utilization for background sync tasks?
It may help to know that I'm running a dual-monitor setup, with Lightroom on a 27" 2560x1440 display maximized to fit the display (2nd display not running LR's 2nd monitor). Since I'm using a retina iPad, the optimal Standard Previews resolution should be the same at 2880 pixels.
Thanks again for the help!

Extremely High cpu usage on battery only

my macbook pro 7,1 revision runs extremely slow on battery and the system is all jumpy, it is fine on mains power.
i have booted in safe mode and this seems to solve the problem
in activity monitor the kernel task process is showing between 160-180% cpu usage
i have done a pram reset and a smc to no avail
any help would be much apreciated
Dave

The only suggestion I can give you is to launch the Console utility and look for messages that might explain the problem. If nothing there jumps out, I have no other ideas.

Extremly high CPU Usage using Bootcamp, XP

I have a MPB 2.5 duo core with 2 Gig RAM and a 8600 Gforce video card.
Ok so I installed XP Pro. using bootcamp to split my HD. Here is my problem.
When I first start up windows it has its usual spike of the CPU to around 40% or so. If I open up internet explorer it will run a little high at around 15%. If I open up Pandora that is where the problem starts. With Pandora open it will have a CPU usage of around 30 to 40% and more noticably the audio will speed up and slow down and as you might guess this causes problems with the streaming of the audio. If I run any game or anything graphics intensive it will run at a steady 90 to 100% CPU usage cauing it to lag ang glitch and the fan to be running all the time.
The weird thing is that on Leopard it will run perfectly. I was thinking the problem may be something to do with the drivers or the hardware.
Help Please!
Adam Melrose

Adam:
I just started experiencing the same problem today. Did you get an answer on what this might be?
Tedd Kidd

Extremely High CPU Usage

Hello! I've been using skype for a very long time and never had any problems with it until about a day or two ago. I don't know if it's a new version of skype causing it, but I've tried uninstalling it and re-installing new ones, old ones, anything to fix this problem.
Everytime I start Skype up, it works fine for about 2-3 minutes, and then the CPU & Memory the program takes in my Windows Task Manager starts to climb, getting to about 20-30% and 200k-300k memory before it freezes entirely and I'm force to end the process. I'm at my wit's end trying to figure this out. I've searched online for fixes and I've tried everything from changing my default browser to IE, to turning off automatic updates, to running as an administrator, or even in Compatibility mode in Windows XP Service Pack 3 Mode.
Any solution's to bringing skype's CPU usage back down to 01-10 would be greatly appreciated.

Try to use these MSI versions.
http://download.skype.com/msi/SkypeSetup_6.16.0.105.msi
http://download.skype.com/msi/SkypeSetup_6.18.0.105.msi
http://www.skype.com/go/getskype-msi
Note: Ensure to turn off Automatic updates.
Our greatest weakness lies in giving up. The most certain way to succeed is always to try just one more time.
If you found my post useful, please give "Kudos".
If it helped to answer your problem/question, please mark it as "Accepted Solution" so other people can find it easily.

[Solved] Empty optical drive = high CPU usage

Hello,
I have been a Gentoo user for 4 years and have installed Arch on my new laptop. The install went well and my system is nearly trouble-free. The problem I'm having is that both of my CPU cores idle at 25-30% when the combo drive is empty. When I put a CD in the drive, both cores idle at 2-3%.
It appears to be a udev problem. The hal-disable-polling command didn't help (yes, I restarted hal), and top shows me this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
19473 root 20 0 266m 111m 13m R 5 2.9 1:33.85 X
654 root 18 -2 6156 840 428 R 4 0.0 1:36.15 udevd
479 root 15 -5 0 0 0 S 2 0.0 0:44.57 scsi_eh_1
2443 aaron 20 0 298m 24m 13m S 1 0.6 0:03.11 konsole
3758 aaron 20 0 70148 4044 2828 S 1 0.1 0:41.02 conky
29169 aaron 20 0 447m 34m 23m R 1 0.9 0:29.03 kwin
1 root 20 0 3796 668 576 S 0 0.0 0:00.27 init
It seems that udevd process is the one looking at the combo drive. What else do I need to look at to fix this problem?
Edit: I forgot to mention that I'm not getting any relevant spam in my messages.log.
Last edited by AaronD (2009-10-08 01:36:40)

This is a known bug in the current version of udev. See this thread for workarounds.

FMS 4 configuration / High CPU usage problem

I am seeing extremly high CPU usage issues with the FMS 4 server. It seems to be a problem with the FMS Edge process? If you start and stop the service, the processor goes back to normal operations.
Looking in the Windows Event logs I am seeing these errors:
Bad network data; terminating connection : bad chunk version 104 on input stream 00000000077A2E80
Also:
Bad network data; terminating connection : (Adaptor: _defaultRoot_, VHost: Unknown, IP: , App: , Protocol: tunnel) : h o s t = % 2 2 % 2 0 % 2 D F O O B A R % 7 C e c h o % 2 0 % 2 2 % 2 0 S h a r e n a m e % 2 2 % 0 A e c h o % 0 A e c h o % 2 0 % 2 2 % 2 0 % 2 0 S o m e S h a r e % 2 0 % 2 0 D i s k % 2 0 % 2 2 % 6 0 i d % 6 0 % 2 0 % 2 3 % 2 2
Can someone shed some light on what might be causing these issues?
Running on a virtual server/ Win2k8R2
Thanks, Tandrist

Hi
Can you please provide us some little more environment information on this issue, like:
- what were you trying to do when you saw this issue, if there was a live telecast or if that was a simple vod workflow?
- What publisher application were you using to send livestream to FMS?
- were you also doing some kind of recording while doing live streaming??
- In case of live streaming what audio/video encoding and bitrates was there in use?
- how many number of connections were there?
- What amount of cpu and mem usage was there (when you say very high cpu usage).. you can see it using task manager
It will help if you can also share your fms logs (inside fms_install_folder/logs) so that we can see if something abnormal was going on there..

Skype vdeo call and high cpu usage on Mac

Hello,
I have seen many posts around skype video call causing extremely high CPU usage which in turn causes a lot of heat and fan starts to go crazy. This does not seem to happen on Windows. I have trawled various forums and tried everything but to no avail.
Finally the workaround that worked for me was simple - during a call when CPU usage is going through the roof and the fans going crazy - just share your screen for a few seconds with the caller and then unshare. CPU usage dramatically falls off and stabilises at around 38% to 40%. I have noticed this my Macbook Pro (2013 2.3ghz, 16gb RAM) running Yosemite.
This is definitely a problem with Skype. Guys; please fix....

Did the sharing and unsharing of screen stabilise your CPU usage? I also tried deleting the Library/Caches/com.skype* directory and whilst it helped initially, in the long run it did not work. The only thing that worked for me was sreen share and unshare.
Personally I am just getting more and more disappointed with OS X. The way they have implemented HiDPI support with scaling (downscaling and then upscaling) is just insane and a lot of applications struggle. I am sure this is not the root cause of the high CPU usage issue for Skype. It's not long before I come off the Apple ecosystem altogether.

[SOLVED] qemu-kvm high cpu usage when using pulseaudio alsa-plugin

My Arch system is configured to use pulseaudio. When an application connects to the sound server it will use either a native pulseaudio driver, or the pulseaudio alsa-plugin if it using a alsa driver.
qemu-kvm in 'extra' is not compiled with native pulseaudio support. When running guests with sound hardware support, qemu-kvm connects to the sound server using the pulseaudio alsa-plugin.
The problem I'm seeing is high cpu usage on the Arch host even though cpu usage on the guest is low. Also, the guest is often unresponsive for a period of time when opening sound applications like the mixer or playing audio.
My solution is to recompile qemu-kvm with native pulseaudio support. This eliminates the use of the pulseaudio alsa-plugin on the Arch host and fixes the above problems.
An easy was to do this is run:
yaourt -S qemu-kvm --build
And edit the PKGBUILD changing the line:
--audio-drv-list=alsa,sdl,oss,esd \
To:
--audio-drv-list=pa,alsa,sdl,oss,esd \
Finish building and install. Don't forget to add yourself to the kvm group.
Last edited by bytesize (2010-08-16 02:34:08)

Problem disappeared.
I'm not sure, but i think installing xf86-video-modesetting helped to fix this issue.
I had an error messages in /var/log/Xorg.0.log like this:
(EE) Failed to load module "modesetting" (module does not exist, 0)

High CPU usage - Rapid Battery Drain - Running HOT

Looking for help.. PLEASE!
Z10 - Model STL100-3 Software release 10.2.1.2179
Symptoms;
Occasionally, and for no apparent reason, I notice my Z10 getting hot in my pocket. I run the device monitor App and see a very high CPU usage, which consequently drains the batter very quickly.
I've tried all the solutions from every support group thread and blog. And I mean ALL!
Pulling the battery
Replaced the battery
Removed the SIM
Deleted G Mail
Removed all 3rd party Apps (2)
Stopped email sync
Stopped calendar sync
Turned off all radio
Turned Off Wi-Fi
Let it sit for hours, even days to let it finish doing whatever its trying to do
Etc Etc Etc.
Finally, I called BB support, they wanted $50 to talk to someone. I told them the issue, they said the device is bad and must be replaced. I said its software related!! They said.. no, its a hardware issue. Device is under warranty and they want me to just go get a new one. I don't want a new one, I want a fix! Stop the waste of BB $
Temporary solution
Eventually, I decided I would do a restore, back to the factory settings, and here's when I found something
I run BB Link, connect the device, do a back-up... and LOW AND BEHOLD.. this fixes the high CPU usage and the device runs great, very cool, low cpu and extremely long battery life.
Sadly! .. this problem reoccurs, after a few days, sometimes after a couple of weeks and just out of the blue.
I can force this fault to occur, simply by doing a restart of the device. Sure enough, it will run hot, use all the cpu and I will have to do a back-up to get it to settle down again. I've tried to wait for the so called 'indexing' to finish, but it never stops running with high cpu and doesn't help.
Can any one tell me whats happening and how to make this a permanent fix?
There are hundreds if not thousands of people having very similar issues, and many different methods to fix it. Its my belief that there is an underlying bigger problem that relates to all these differing fixes, but as yet.. I cant find it and none of these fixes work for me. For now... I will keep doing the occasional back-up and hope I get a response that can help.
Thanks to all that read this.

curve8530curve8330 wrote:
The heat may be normal. After a little water damage incident, which I repaired, I disassembled my Z10 the find a small heat sink will thermal compound. This helps dissipate heat efficiently. I found a large number of air bubbles and possibly a large air pocket by the way the paste stuck to both sides. I removed the old paste and replaced it with artic silver paste and the z10 has been much much cooler. It use to run about 105*f and now it is around 85*f.
See this thread I posted for before and after pictures using a thermal imager.
http://supportforums.blackberry.com/t5/BlackBerry-Z10/Z10-heating-up-fix/m-p/3031220#M71390
@Curve8530 .....as much a s your discovery is appreciated, I hardly believe that most people will actually dismantle their phone to remove the paste and replace with arctic silver. Besides, what you are doing is not a fix for the actual problem....
In most cases, this heat is associated with apps using the CPU resources beyond the normal limits.
As an easy fix, finding and removing the app(s) in question followed by a reboot, solves the issue. In some cases an OS reload is necessary.... but under no circumstances I would even remotely suggest to any member to dismantle their phone and do what you did...

/sbin/init high CPU usage (80%)

My PC run slowly, I viewed the processes by htop utility and it revealed that /sbin/init has a constantly high CPU usage, around 70-80%. I scanned it with clamscan virus scanner, but not infected. What can I do to fix this problem?

Did you mean "ps -ef" ? Then:
UID PID PPID C STIME TTY TIME CMD
root 1 0 8 Sep22 ? 08:27:41 /usr/lib/systemd/systemd --system --deserialize 131
root 2 0 0 Sep22 ? 00:00:00 [kthreadd]
root 3 2 0 Sep22 ? 00:45:38 [ksoftirqd/0]
root 5 2 0 Sep22 ? 00:00:00 [kworker/0:0H]
root 7 2 0 Sep22 ? 00:05:10 [rcu_preempt]
root 8 2 0 Sep22 ? 00:00:03 [rcu_sched]
root 9 2 0 Sep22 ? 00:00:00 [rcu_bh]
root 10 2 0 Sep22 ? 00:00:02 [migration/0]
root 11 2 0 Sep22 ? 00:00:01 [watchdog/0]
root 12 2 0 Sep22 ? 00:00:01 [watchdog/1]
root 13 2 0 Sep22 ? 00:00:02 [migration/1]
root 14 2 0 Sep22 ? 00:54:35 [ksoftirqd/1]
root 16 2 0 Sep22 ? 00:00:00 [kworker/1:0H]
root 17 2 0 Sep22 ? 00:00:00 [khelper]
root 18 2 0 Sep22 ? 00:00:00 [kdevtmpfs]
root 19 2 0 Sep22 ? 00:00:00 [netns]
root 20 2 0 Sep22 ? 00:00:00 [khungtaskd]
root 21 2 0 Sep22 ? 00:00:00 [writeback]
root 22 2 0 Sep22 ? 00:00:00 [ksmd]
root 23 2 0 Sep22 ? 00:00:52 [khugepaged]
root 24 2 0 Sep22 ? 00:00:00 [crypto]
root 25 2 0 Sep22 ? 00:00:00 [kintegrityd]
root 26 2 0 Sep22 ? 00:00:00 [bioset]
root 27 2 0 Sep22 ? 00:00:00 [kblockd]
root 30 2 0 Sep22 ? 00:05:54 [kswapd0]
root 31 2 0 Sep22 ? 00:00:00 [fsnotify_mark]
root 35 2 0 Sep22 ? 00:00:00 [kthrotld]
root 36 2 0 Sep22 ? 00:00:00 [ipv6_addrconf]
root 37 2 0 Sep22 ? 00:00:00 [deferwq]
root 63 2 0 Sep22 ? 00:00:00 [khubd]
root 64 2 0 Sep22 ? 00:00:00 [firewire]
root 65 2 0 Sep22 ? 00:00:00 [firewire_ohci]
root 66 2 0 Sep22 ? 00:00:00 [ata_sff]
root 68 2 0 Sep22 ? 00:00:00 [scsi_eh_0]
root 69 2 0 Sep22 ? 00:00:00 [scsi_tmf_0]
root 70 2 0 Sep22 ? 00:00:00 [scsi_eh_1]
root 71 2 0 Sep22 ? 00:00:00 [scsi_tmf_1]
root 74 2 0 Sep22 ? 00:00:00 [scsi_eh_2]
root 75 2 0 Sep22 ? 00:00:00 [scsi_tmf_2]
root 76 2 0 Sep22 ? 00:00:00 [scsi_eh_3]
root 77 2 0 Sep22 ? 00:00:00 [scsi_tmf_3]
root 88 2 0 Sep22 ? 00:01:22 [kworker/0:1H]
root 89 2 0 Sep22 ? 00:00:00 [scsi_eh_4]
root 90 2 0 Sep22 ? 00:00:00 [scsi_tmf_4]
root 91 2 0 Sep22 ? 00:00:07 [usb-storage]
root 99 2 0 Sep22 ? 00:00:00 [kworker/1:1H]
root 101 2 0 Sep22 ? 00:00:27 [jbd2/sda1-8]
root 102 2 0 Sep22 ? 00:00:00 [ext4-rsv-conver]
root 130 1 0 Sep22 ? 00:08:22 /usr/lib/systemd/systemd-journald
root 145 2 0 Sep22 ? 00:00:00 [rpciod]
root 147 2 0 Sep22 ? 00:00:00 [nfsiod]
root 163 1 0 Sep22 ? 00:00:00 /usr/lib/systemd/systemd-udevd
root 221 2 0 Sep22 ? 00:00:00 [kpsmoused]
root 243 1 1 Sep22 ? 01:39:24 /sbin/mount.ntfs-3g /dev/sda2 /mnt/ntfs -n -o rw,uid=1000,gid=100,dmask=022,fmask=133
root 251 1 0 Sep22 ? 00:00:34 /usr/lib/systemd/systemd-logind
dbus 253 1 0 Sep22 ? 00:02:38 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root 254 1 0 Sep22 ? 00:02:32 /usr/bin/haveged -w 1024 -v 1
root 255 1 0 Sep22 ? 00:00:00 /usr/bin/dhcpcd -q -b
rpc 258 1 0 Sep22 ? 00:00:00 /usr/bin/rpcbind -w
root 288 1 0 Sep22 ? 00:00:13 /usr/bin/NetworkManager --no-daemon
root 295 1 0 Sep22 ? 00:00:00 /usr/sbin/rpc.idmapd
root 330 2 0 Sep22 ? 00:00:00 [cfg80211]
polkitd 333 1 0 Sep22 ? 00:00:09 /usr/lib/polkit-1/polkitd --no-debug
tor 436 1 0 Sep22 ? 00:03:27 /usr/bin/tor -f /etc/tor/torrc
privoxy 438 1 0 Sep22 ? 00:00:00 /usr/bin/privoxy --pidfile /run/privoxy.pid --user privoxy.privoxy /etc/privoxy/config
root 445 1 0 Sep22 ? 00:00:00 /usr/sbin/rpc.statd --no-notify
root 449 1 0 Sep22 ? 00:00:00 /usr/sbin/rpc.mountd
root 466 2 0 Sep22 ? 00:00:00 [nfsv4.0-svc]
root 500 1 0 Sep22 ? 00:00:00 /usr/sbin/lxdm-binary
root 503 500 6 Sep22 tty7 06:37:07 /usr/bin/Xorg.bin :0 vt07 -nolisten tcp -novtswitch
root 1755 500 0 Sep22 ? 00:00:00 /usr/lib/lxdm/lxdm-session
walaki 1756 1 0 Sep22 ? 00:00:00 /usr/lib/systemd/systemd --user
walaki 1757 1756 0 Sep22 ? 00:00:00 (sd-pam)
walaki 1763 1755 0 Sep22 ? 00:00:00 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc
walaki 1773 1 0 Sep22 ? 00:00:00 dbus-launch --sh-syntax --exit-with-session
walaki 1774 1 0 Sep22 ? 00:00:21 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
walaki 1781 1763 0 Sep22 ? 00:00:46 xfce4-session
walaki 1784 1 0 Sep22 ? 00:00:00 /usr/lib/xfce4/xfconf/xfconfd
walaki 1789 1 0 Sep22 ? 00:00:16 /usr/bin/gpg-agent --sh --daemon --enable-ssh-support --write-env-file /home/walaki/.cache/gpg-agent-info
walaki 1792 1781 0 Sep22 ? 00:01:54 xfwm4 --display :0.0 --sm-client-id 23fec2b63-e849-4a72-8ded-64b47902bd41
walaki 1795 1781 0 Sep22 ? 00:00:35 Thunar --sm-client-id 2d0147b28-0a91-4a3b-a669-064fc26ae553 --daemon
walaki 1797 1781 0 Sep22 ? 00:09:43 xfce4-panel --display :0.0 --sm-client-id 247d7309b-f81b-4064-adbd-0875fed923d4
walaki 1798 1781 0 Sep22 ? 00:00:18 xfdesktop --display :0.0 --sm-client-id 2e572e480-670a-4c6f-af62-2339f19929ef
walaki 1799 1 0 Sep22 ? 00:00:36 xfsettingsd --display :0.0 --sm-client-id 26269b48e-af0b-4399-b385-5305502e24f1
walaki 1802 1781 1 Sep22 ? 01:24:09 /usr/lib/skype/skype -session 21d1f7d38-8c0a-41de-98b7-021e4f2a5bd7_1410900031_251500
walaki 1803 1781 0 Sep22 ? 00:00:06 kruler -session 20c051002-8d7b-4c2c-bf0b-c384f149b9b5_1410900031_629257
walaki 1806 1 0 Sep22 ? 00:00:01 xfce4-power-manager --restart --sm-client-id 2154ad16d-be90-40bc-8354-c2647728cf16
walaki 1810 1 0 Sep22 ? 00:00:00 /usr/lib/gvfs/gvfsd
walaki 1823 1 0 Sep22 ? 00:00:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
walaki 1825 1797 0 Sep22 ? 00:00:02 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libsystray.so 6 14680094 systray Notification Area Area where notification icons appear
walaki 1833 1797 0 Sep22 ? 00:00:07 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libmixer.so 15 14680095 mixer Audio Mixer Adjust volume levels
walaki 1834 1797 0 Sep22 ? 00:44:27 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libweather.so 16 14680096 weather Weather Update Show current weather conditions
walaki 1835 1797 0 Sep22 ? 00:46:02 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libsystemload.so 17 14680097 systemload System Load Monitor Monitor CPU load, swap usage and memory footprint
walaki 1836 1797 0 Sep22 ? 00:00:03 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libactions.so 2 14680098 actions Action Buttons Log out, lock or other system actions
walaki 1841 1797 0 Sep22 ? 00:00:03 /usr/lib/xfce4/panel/wrapper /usr/lib/xfce4/panel/plugins/libthunar-tpa.so 8 14680102 thunar-tpa Trash Applet Display the trash can
walaki 1843 1 0 Sep22 ? 00:00:04 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
walaki 1846 1 0 Sep22 ? 00:00:03 /usr/lib/gvfs/gvfsd-trash --spawner :1.9 /org/gtk/gvfs/exec_spaw/0
root 1856 1 0 Sep22 ? 00:00:00 /usr/lib/upower/upowerd
root 1857 1 0 Sep22 ? 00:02:10 /usr/lib/udisks2/udisksd --no-debug
walaki 1862 1 0 Sep22 ? 00:09:10 kwooty -session 2fc05dbf4-9492-4cf1-bd80-efe7e47dfb90_1410900031_251208
walaki 1895 1 0 Sep22 ? 00:00:00 /usr/lib/GConf/gconfd-2
walaki 1904 1 0 Sep22 ? 00:00:05 /usr/bin/python2 /usr/bin/glipper
walaki 1907 1 0 Sep22 ? 00:00:06 nm-applet
walaki 1922 1 0 Sep22 ? 00:00:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
walaki 1926 1922 0 Sep22 ? 00:00:25 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
walaki 1930 1 0 Sep22 ? 00:00:03 /usr/lib/evolution/3.12/evolution-alarm-notify
walaki 1936 1 1 Sep22 ? 01:59:26 firefox
walaki 1938 1 0 Sep22 ? 00:01:08 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
walaki 2023 1 0 Sep22 ? 00:00:00 /usr/lib/evolution-data-server/evolution-source-registry
walaki 2043 1 0 Sep22 ? 00:00:25 /usr/lib/gnome-online-accounts/goa-daemon
walaki 2058 1 0 Sep22 ? 00:00:01 /usr/lib/evolution-data-server/evolution-calendar-factory
walaki 2084 1 0 Sep22 ? 00:00:00 kdeinit4: kdeinit4 Runnin e
walaki 2089 2084 0 Sep22 ? 00:00:00 kdeinit4: klauncher [kdei e
walaki 2101 1 0 Sep22 ? 00:00:06 kdeinit4: kded4 [kdeinit]
walaki 5752 1 0 Sep22 ? 00:00:01 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
walaki 5887 1789 0 Sep22 ? 00:01:01 scdaemon --multi-server
walaki 7557 11505 0 11:19 pts/8 00:00:00 /bin/bash
walaki 8876 19571 0 12:04 pts/4 00:00:03 mc
walaki 8878 8876 0 12:04 pts/9 00:00:00 bash -rcfile .bashrc
root 10950 2 0 18:10 ? 00:00:02 [kworker/u4:1]
walaki 10953 18727 0 18:10 pts/6 00:00:04 mc
walaki 10955 10953 0 18:10 pts/7 00:00:00 bash -rcfile .bashrc
walaki 11492 1797 0 Sep23 ? 00:02:06 /usr/bin/python2 /usr/bin/terminator
walaki 11504 11492 0 Sep23 ? 00:00:00 gnome-pty-helper
walaki 11505 11492 0 Sep23 pts/8 00:00:00 /bin/bash
walaki 12283 1797 0 13:19 ? 00:00:26 /usr/bin/python2 /usr/bin/terminator
walaki 12299 12283 0 13:19 ? 00:00:00 gnome-pty-helper
walaki 12300 12283 0 13:19 pts/1 00:00:00 /bin/bash
walaki 12707 1797 0 13:23 ? 00:02:59 geany
walaki 12713 12707 0 13:23 ? 00:00:00 gnome-pty-helper
walaki 12714 12707 0 13:23 pts/11 00:00:00 /bin/bash
walaki 13471 1797 0 18:31 ? 00:00:18 /usr/bin/python2 /usr/bin/terminator
walaki 13487 13471 0 18:31 ? 00:00:00 gnome-pty-helper
walaki 13488 13471 0 18:31 pts/3 00:00:00 /bin/bash
walaki 13751 13488 0 18:33 pts/3 00:00:00 /bin/bash
walaki 16906 1797 46 13:59 ? 04:12:08 /usr/lib/opera-next/opera-next
walaki 18711 1797 0 Sep23 ? 00:05:05 /usr/bin/python2 /usr/bin/terminator
walaki 18726 18711 0 Sep23 ? 00:00:00 gnome-pty-helper
walaki 18727 18711 0 Sep23 pts/6 00:00:00 /bin/bash
walaki 19550 1797 0 Sep22 ? 00:01:48 /usr/bin/python2 /usr/bin/terminator
walaki 19570 19550 0 Sep22 ? 00:00:00 gnome-pty-helper
walaki 19571 19550 0 Sep22 pts/4 00:00:00 /bin/bash
walaki 21931 23464 3 20:17 ? 00:04:59 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.24.769536197
walaki 22985 23464 0 20:39 ? 00:00:55 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.25.841939391
walaki 23052 23464 2 20:40 ? 00:03:57 /opt/google/chrome/chrome --type=ppapi --channel=23445.26.1843768387 --ppapi-flash-args --lang=en-US
walaki 23445 1 3 15:02 ? 00:16:57 /opt/google/chrome/chrome
walaki 23453 23445 0 15:02 ? 00:00:05 /opt/google/chrome/chrome --type=sandbox-ipc
walaki 23454 23445 0 15:02 ? 00:00:00 /opt/google/chrome/chrome-sandbox /opt/google/chrome/chrome --type=zygote
walaki 23455 23454 0 15:02 ? 00:00:00 /opt/google/chrome/chrome --type=zygote
walaki 23461 23455 0 15:02 ? 00:00:00 /opt/google/chrome/chrome-sandbox /opt/google/chrome/nacl_helper
walaki 23462 23461 0 15:02 ? 00:00:00 /opt/google/chrome/nacl_helper
walaki 23464 23455 0 15:02 ? 00:00:00 /opt/google/chrome/chrome --type=zygote
walaki 23484 23445 0 15:03 ? 00:00:04 /opt/google/chrome/chrome --type=gpu-process --channel=23445.0.587379006 --supports-dual-gpus=false --gpu-driver-bug-workarounds=1,14,20,23,43 --disable-accelerated-video-decode --gpu-vendor-id=0x10de --gpu-device-id=0x0322 --gpu-driver-vendor --gpu-driver-version
walaki 23672 23464 0 15:04 ? 00:01:06 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.5.858801638
root 23962 288 0 Sep25 ? 00:00:00 /usr/bin/dhclient -d -sf /usr/lib/networkmanager/nm-dhcp-helper -pf /var/run/dhclient-enp2s8.pid -lf /var/lib/NetworkManager/dhclient-a8966a98-c9d9-4425-9e4d-459c41d83921-enp2s8.lease -cf /var/lib/NetworkManager/dhclient-enp2s8.conf enp2s8
root 24159 1 0 15:08 tty2 00:00:00 /sbin/agetty --noclear tty2 linux
root 24165 1 0 15:08 tty3 00:00:00 /sbin/agetty --noclear tty3 linux
root 24169 1 0 15:08 tty5 00:00:00 /sbin/agetty --noclear tty5 linux
root 24174 1 0 15:08 tty6 00:00:00 /sbin/agetty --noclear tty6 linux
walaki 25161 1 2 Sep23 ? 02:22:03 audacious
root 25840 2 0 21:32 ? 00:00:01 [kworker/1:1]
walaki 27082 23464 4 21:51 ? 00:02:56 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.29.1207326524
root 27424 2 0 22:00 ? 00:00:00 [kworker/0:1]
root 27664 2 0 15:42 ? 00:00:04 [kworker/u4:2]
root 27769 2 0 22:07 ? 00:00:00 [kworker/1:2]
walaki 28865 1 0 Sep25 ? 00:00:00 /usr/lib/gvfs/gvfsd-http --spawner :1.9 /org/gtk/gvfs/exec_spaw/1
walaki 29628 8878 0 22:54 pts/9 00:00:02 /usr/bin/ruby /home/walaki/util/mr1 Nekem az ég - hazafutás
walaki 29652 23464 0 22:54 ? 00:00:00 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AutoReloadExperiment/Enabled/ChromeSuggestions/Most Likely with Kodachrome/ExtensionInstallVerification/None/OmniboxBundledExperimentV1/StandardR4/Prerender/PrerenderEnabled/PrerenderFromOmnibox/OmniboxPrerenderEnabled/PrerenderLocalPredictorSpec/LocalPredictor=Disabled/SPDY/SpdyDisabled/SettingsEnforcement/no_enforcement/Test0PercentDefault/group_01/UMA-Dynamic-Binary-Uniformity-Trial/default/UMA-New-Install-Uniformity-Trial/Experiment/UMA-Population-Restrict/normal/UMA-Session-Randomized-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-1-Percent/group_22/UMA-Uniformity-Trial-10-Percent/group_05/UMA-Uniformity-Trial-100-Percent/group_01/UMA-Uniformity-Trial-20-Percent/group_03/UMA-Uniformity-Trial-5-Percent/group_14/UMA-Uniformity-Trial-50-Percent/default/VoiceTrigger/Install/ --renderer-print-preview --enable-offline-auto-reload --enable-threaded-compositing --enable-delegated-renderer --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=23445.30.161699173
root 29693 2 0 22:55 ? 00:00:00 [kworker/0:2]
root 29915 2 0 23:00 ? 00:00:00 [kworker/0:0]
root 29930 27664 89 23:00 ? 00:00:31 /usr/lib/systemd/systemd-coredump 29431 1000 100 6 1411765249 wavparse1374:si
walaki 29946 10955 0 23:01 pts/7 00:00:00 ps -ef
walaki 29948 10955 0 23:01 pts/7 00:00:00 leafpad
walaki 30148 1 0 Sep23 ? 00:00:00 /usr/lib/dconf/dconf-service
walaki 30523 1 0 Sep25 ? 00:00:00 /bin/sh /home/walaki/jdownloader/JDLauncher
walaki 30544 30523 0 Sep25 ? 00:04:54 /usr/lib/jvm/java-default-runtime/bin/java -Dinstall4j.jvmDir=/usr -Dexe4j.moduleName=/home/walaki/jdownloader/JDLauncher -Xmx512m -Xms64m -Dinstall4j.launcherId=26 -Dinstall4j.swt=false -Di4j.vmov=true -Di4j.vmov=true -Di4j.vmov=true -Di4j.vmov=true -Di4j.vmov=true -Di4j.vpt=true -classpath /home/walaki/jdownloader/.install4j/i4jruntime.jar:/home/walaki/jdownloader/JDownloader.jar com.install4j.runtime.launcher.Launcher launch jd.Main true false true true false true true 0 0 20 20 Arial 0,0,0 8 500 version 0.9 20 40 Arial 0,0,0 8 500 -1

High CPU Usage On client application when upgrade remote SQL database

Hi,
Is anyone here encountered very high CPU usage after upgraded the database from SQL 2005 to SQL 2012? Following describes my issue.
I have my client application running on Windows 7 that access to central database (SQL 2005) on Windows server 2003 using ODBC connection, this client application basically query data and perform data insert and update. There are a number of this similar
clients connected to the database.
Due to slowness of the database server, company decided to upgrade the database server to SQL 2012 and also new hardware runing Windows Server 2012. There is no change on the client application and client hardware and the client application still using the
same ODBC connection to query, insert or update the new database server.
The problem I am now experiencing now is that my client PC where my client application running the CPU usage is very high almost hitting 100% when accessing to the central database. I am also noticed this program lsass.exe that utilized almost 40-50% of
the CPU time when client application accessing the central database.
Is anyone here know, why client PC CPU usage 100% when access to upgraded SQL 2012 database? What is lsass.exe program doing, it only appear when accessing to database server. How to reduce the CPU usage on client?
Thanks.
Chee Wee.

Hello,
After upgrading, please rebuild indexes and update statistics on the databases.
http://www.mssqltips.com/sqlservertip/1367/sql-server-script-to-rebuild-all-indexes-for-all-tables-and-all-databases/
http://www.mssqltips.com/sqlservertip/1606/execute-update-statistics-for-all-sql-server-databases/
Configure maxdop on the instance.
http://blogs.msdn.com/b/sqlsakthi/archive/2012/05/24/wow-we-have-maxdop-calculator-for-sql-server-it-makes-my-job-easier.aspx
If the above does not solve the issue, let us know.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

High CPU usage (more than 100%) while running video applications

Hello everyone,
I desperately need help with this.
I have a late 2007 White Macbook running Mac OS X 10.6.8 :
Model Name:          MacBook
Model Identifier:          MacBook2,1
Processor Name:          Intel Core 2 Duo
Processor Speed:          2 GHz
Number Of Processors:          1
Total Number Of Cores:          2
L2 Cache:          4 MB
Memory:          3 GB
Bus Speed:          667 MHz
The issue that I am having is, whenever I play a video (Netflix/Silverlight player, YouTube, Skype, etc.) the CPU usage shoots up above 100% and the video or the video chat becomes VERY choppy. It becomes impossible to keep going once that starts. Originally I had 1Gb RAM (512 + 512) ... then I upgraded to (1GB + 512mb) ... it was fine for about a year and then started chocking on memory... so recently I made it (1GB +2GB) and that's when this high CPU usage thing started (according to my knowledge)
I have had this machine since last 4 years and its very dear to me. I dont wanna buy a new one. I will really appreciate if someone could help.

I am spending sleepless nights, researching for a fix. From what I found so far, a considerable amount of people were able to fix this issue by simple cleaning the insides of their machines using air dusters, especially the fans. I don't know how cleaning would help with CPU utilization, but by interpolation, I feel it's worth a try. At least it will be clean, if not perfectly functional. lol
Now the next big challenge ahead of me is getting the screws on my Macbook open. I was following the Fan Repair Guide on ifixit.com. I went and got the #00 Phillips screwdriver as suggested in the guide... came home and found out the screwdriver is too big.... went back got a #0000 Phillips (I also found out that screwdrivers with same number might be of different sizes in different stores)... got a couple of screws out and then--- another road-block!! there are a few extremely tiny Phillips screws on my macbook. Now I am hunting for the smallest Phillips screwdriver in the world. Hopefully, I will find it in some watch repair or eye-glasses repair kit in a store such as CVS or Walgreens... aaaah... this is sooo frustrating!!! I just want to get his done so that I can check it off the list of probable solutions that I want to try. Will update here if this works.
From what you say, I think that the Silverlight upgrade might be the culprit in my case too. But the effect is there also for Youtube, Skype , or any other Video/Graphics intensive application that I use. Although, Silverlight/Netflix performs the worst among all the apps.
I love my Macbook... don't want to part with it.

Kernel_task high CPU usage yosemite

Hi,
I have a problem with my old macbook pro 15" Early 2011
The battery was dead so I bought a new one and replaced it. I also installed a new Samsung SSD.
Then after the startup (OSX Mavericks was installed) I had a high CPU usage on the kernel_task process.
After some research i managed to get rid of the problem with manipulating the IOPlatformPluginFamily.kext files.
After that everything worked fine.
Now I decided to upgrade to Yosemite (clean install from usb) and now i have the same problem again, but i can't find the IOPlatformPluginFamily.kext.
After I power up the macbook everything works fine, but after some minutes the kernel_task has again a very high CPU usage - the mouse is hardly moving.
How can I solve this problem and where do I find the IOPlatformPluginFamily.kext? Is there another solution for this problem?
I already reset the SMC and the NVRAM.
thank you
Hans

Hi,
I have a problem with my old macbook pro 15" Early 2011
The battery was dead so I bought a new one and replaced it. I also installed a new Samsung SSD.
Then after the startup (OSX Mavericks was installed) I had a high CPU usage on the kernel_task process.
After some research i managed to get rid of the problem with manipulating the IOPlatformPluginFamily.kext files.
After that everything worked fine.
Now I decided to upgrade to Yosemite (clean install from usb) and now i have the same problem again, but i can't find the IOPlatformPluginFamily.kext.
After I power up the macbook everything works fine, but after some minutes the kernel_task has again a very high CPU usage - the mouse is hardly moving.
How can I solve this problem and where do I find the IOPlatformPluginFamily.kext? Is there another solution for this problem?
I already reset the SMC and the NVRAM.
thank you
Hans

(Solved) systemd-journald extremely high CPU usage

Similar Messages

Maybe you are looking for