Unusualy slow openbox system.[Solved]

Hi
I have a rather simple system running on my computer without anything fancy, the things thats constantly running are pidgin, conky, uim, xfce4-panel, skype, xchat and sonata then ether transmission or firefox. The demons I have running are syslog-ng, network, netfs, crond, mpd, alsa, dbus, avahi-deamon, cups and gdm.
For some reason especially Firefox is extremely slow but everything is also rather slow for example startup time of urxvt.
The thing is that my backup system is way faster (Ubuntu with gnome) theres got to be something wrong with ether one of my apps or with my settings, any idea what I have missed?
Last edited by darkclown (2007-07-21 05:44:57)

Ah solved it, I didn't know the top command before but it showed that gdm was sucking up allot of possessor and ram and ones I turned it of everything works nicely
Thanks ataraxia
Last edited by darkclown (2007-07-22 03:25:40)

Similar Messages

Disk is too slow or System Overloaded ERROR

I have logic studio and a macbook pro and keep getting the following error message: Logic Pro: Disk is too slow or System Overloaded (-10010) Not sure how to fix it. Any suggestions?

It's a bug in logic. It's been there since multicore CPUs came out.
Try putting your fx on a bus/aux rather than on the same track as the instrument.
That way it will trick logic into using a different core for the different tracks.
I've seen this problem on dual quad core CPU mac pros, so it has nothing to do with your CPU performance.
Also if your recording to the internal harddrive whilst playing back audio from it you might run into problems when using bfd2 or addictive drums or any other large sample library type plugin.
In my MacBook pro I took the DVD drive out and put in an SSD for the OS in its place.
I then use the internal mechanical drive for recording and samples etc.
This solved all my issues and made everything so much snappier.
It's dead easy to do too. Infact it works so well I'm thinking about getting a standard MacBook pro (so I can do the same thing again) instead of the retina one.
I'd refuse to buy a retina one until I have seen logic play back 1 instance of bfd2 a few audio files whilst at the same time recording a guitar through amplitube 3. I'm not paying £2000 if it can't do that. (you'll be surprised)
Like I said my old one couldn't do it due to the overloads you mention until I did the DVD drive swap trick.
The retina looks good but, 1/4" thinner is one thing, but having to carry leads and adapters for everything it kind of defeats the purpose!
I would need a thunderbolt to FireWire adapter (which aren't out yet) a FireWire 800 lead and a FireWire 800 to 400 adapter jut to plug my apogee duet soundcard in! ***?
I'd buy a thunderbolt audio interface but their are no mobile ones. The only ones that are out are large ones for the studio (And mac pros don't even have thunderbolt)
It makes no sense, no sense at all!
You couldn't make it up. At least they have dropped the dongle from logic so I can plug my mouse in.
Emagic should release a pc version again. These quarterly decade updates are getting boring!
Where's logic X?

Logic Express says "Disk is too slow or system overload (-10010)"

I have a brand spankin new white MacBook. It has Intel Core Duo 2.1 processors, with 2gigs of RAM, and Leopard 10.5.6 OS. I am using Logic Express 8 and every now and then I will get an error message "Disk is too slow or system overload (-10010)
I checked the requirements for Logic Express 8 and I exceed them. Could I still need more than 2 gigs of RAM?

I got the same problem when I was recording 10 tracks while using SW monitoring. For a short while it went OK but then twice in a row I got this message about the disk being too slow. The result was that I got a real loud noise on the headphone. But after that the recording just proceeded. I had to stop because otherwise I think the musicians would have gone deaf. However I had to continue with recording for some more hours so I tried to solve it. The following worked for me. I turned off 24 bit recording because I had the impression there was too much data being written. I also made the buffer as low as possible (32). After that I did not have a problem anymore and recorded for about 7 to 8 hours in a row.
So I suspect that the HD is indeed too slow or has not enough cache. As far as I can see my HD has 8 MB RAM and runs at 5400 rpm. I wll ask Aple support if this could be an issue when recording large amounts of data. Note that I have 4 GB RAM and still got the problem so that is not the cause of this issue here.

Logic 9.1: Disk is too slow or system overload (-10010)

After updating I kept getting this error: Disk is too slow or system overload (-10010)
Can't go five minutes without encountering this. I'm in 32 bit mode using record via rewire. It's maddening and I am now kicking myself for updating. The song that's doing this is a song I was using working on the day before I updated. I had no problems then.
Anyone else encountering this?

I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
Or, you can search the forums for error 10010.
The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
I hope this provides some insight.
Chris

Error message!!!!!Disk is too slow or System Overload this keeps coming up?

Logic Pro:
Disk is too slow or System Overload
(-10010)
Mac book pro
10.5.8 OX
4gigs RAM
recording to ext 800 firewire drive
any ideas???

I am just reposting my response to a similar question because I never found a solution to this problem just a work-around. I would love to know the actual solution.
I have encountered this issue as well. I never solved the issue but did find a work-around. Unfortunately, this temporary solution may not work for more 'heavy' users then I. Although, many have commented that this issue happens even on small projects (as it did with me also), many usually create much bigger projects and are using the smaller projects just as a litmus test. I qualify this because the work-around I discovered is using USB 2.0 to connect my external HDD rather than either of the firewire ports on the drive. So, for those wanting to create larger projects, this solution may not be an option. I won't delve into the details here, but I will include a link to my thread so you can see all the troubleshooting I did and the suggestions that were offered.
http://discussions.apple.com/thread.jspa?threadID=2102925&tstart=0
Or, you can search the forums for error 10010.
The only other items of note I can think to add at this point is I am still on 10.5.8 not SL. Logic 9.1.1, and I recently increased the amount of RAM to 4G. The work-around has been working for me, and I haven't had time to check that any of these updates fixed the problem. But I will soon and will report any changes.
I hope this provides some insight.
Chris

CoreAudio: Disk is too slow or System Overload. (-10010)

I keep getting this error when I'm playing a song that has 16 tracks and effects on each track, but each track is frozen (!): CoreAudio: Disk is too slow or System Overload. (-10010). I'm running a G4 and have 2G RAM. Is this common? What can I do to prevent this? Thanks for any advice you can give!
-David

In addition to Rohan's suggestions you have more options depending on how you work and what phases of the project you are in.
Something overlooked very often is polyphony enabled for the EXS24-some patches are set to 64 drop the polyphony to either the minimum you will need or less (if less you will notice older notes cutting out-but you can set it to the necessary number upon bounce or export). Some mono patches from sound designers are set to 32 or 64-even if you enable unison this is often worthless.
Up your buffer size-I usually have my PBook at 512-I usually do offline editing, location recording and sound design with the book anyways.
Export the track.
Set virtual memory in EXS prefs to 'on' and with the largest RAM allocation-slow disk, lots of activity.
If you use certain exs patches often but only parts of them trimming the excess off the instrument can improve performance. If you have a piano program with good samples you can initially create a lite version with 2 velocity layers and then when it is time to get things sounding good revert the instrument to the original 5 layer-obviously this makes a huge difference depending on what you are using the piano for, leave it if it is critical.
Save the Channel strip and export as audio file while keeping the sequence in your session. Like Freezing but you can manually trim the file start position and set the bit depth. Freeze files render from the start until the last audible sample and then truncate the tails, meaning even if you can't hear it it is still pulling "silence" from disk as long as there is sound after it. Exporting as 24 or 16 bit will effectively reduce your file size by 25 (24bit) or 50 (16bit) percent. If you know you don't have to edit a performance for weeks to come exporting it will solve alot of problems for CPU.
Someone should back me up on this one but at the moment I want to say EXSamples load into memory regardless of freeze settings-reducing your resources.
Disable the filter (if live or playback-N/A with Freeze)-it is often not critical for some patches. The more synthetic sounds or sounds with fewer/shorter samples rely on them.
Disable Unison.
Most sample libraries were not recorded at 88/96k-there is no benefit in running them in sessions in these Sampling rates as far as the EXS sound quality goes.
That should keep you busy for a while, just some tuning to up your system performance.

Error message: "Disk is too slow or System Overload."

When I try to record from the line-in on my MacBook Pro (2.16GHz, 2GB RAM, 100GB 7200rpm HD), I get after some time (that can range from a few seconds to a few minutes) the error message: "CoreAudio: Disk is too slow or System Overeload. (-10010)".
This is weird because I get that error even when recording into an empty project. I have no such error on my old PowerBook G4 (867MHz, 512MB RAM) with the same version of Logic Express (most recent). Both computers are fully up-to-date.
I also get that error on my MacBook Pro very often when I'm working on a project and it's getting pretty annoying, it sorts of halts the process each time...
I also have Mail, iCal and Adium running at the same time as Logic Express, none of which use much CPU so the problem can't realistically be from them...
Any help to resolve this issue or at least shed some light on the potential cause would be greatly appreciated!

Simply having idle applications in the background is probably fine, but I certainly believe that something like Mail checking for new messages in the middle of recording in Logic could cause problems.
I would also check Activity Monitor to see if you have any background processes running that you aren't aware of. My wife's iBook slowed to a crawl once, and I discovered that a printer driver she installed to use a printer at work was using about 80 percent of the CPU.
-Eric

Logic error-hard drive too slow or system overload (new macbook!)

have made a few short tracks with logic with no probs. when i have tried to play the demo songs which have many tracks, i get an error msg saying hd too slow or system overload. i have a new macbook, 2.4, 2mb ram, 250 gb hd (with loads space left). airport turned off when using logic. what gives???

Samples that I am using are located on a 7200 external HD.
Is your external formatted for Mac? If you didn't buy it from a store that sells mac drives specifically, it's probably formatted for windows. You must reformat for Mac or you'll have a lot of performance issues.
I've a Macbook 2,2 Ghz Core 2 DUO with 2Go of RAM.
You should get more Ram, it's really cheap these days.
Airport is disconnected. My AUdio Buffer is 1024 in the Logic preferences.
Make sure the I/O Safety Buffer is OFF, and then set the buffer size at 256 or 512.

I can't go beyond release 3.6 because it slows my system down to a crawl. When I back the upgrade out and go back to 3.6 my system is fine. Any suggestions?

I can't go beyond release 3.6 because it slows my system down to a crawl. When I back the upgrade out and go back to 3.6 my system is fine. Any suggestions?

Does that PC meet Firefox 4.0+ system requirements for hardware? <br />
Firefox 4.0+ versions are considerably different from earlier versions. <br />
http://www.mozilla.com/en-US/firefox/6.0/system-requirements/
* Pentium 4 or newer processor that supports SSE2
* 512MB of RAM
* 200MB of hard drive space

Core Audio Disk too slow or System Overload message

Hi, I hope somebody can help me. I've seen the topics about this already posted, but my situation is a little different. I'm only playing back three tracks of recorded audio and two EXS24 sampler instruments. I have the Logic compressor on my bass track and thats it! My Disk IO meter shows no load at all as well as the audio meter. However, I'm still getting the core audio disk to slow or system overload message. I figure with a dual 2.7 G5 and 2.5 Gigs of ram I should be unstoppable. What's happening?
By the way I'm using Logic Pro 7.1, and my sound card is a Delta 1010 from M-Audio.
Thank You, anybody for your help!
Dual 2.7GHZ PowerMac G5 Mac OS X (10.4) 2.5 Gigs of ram

Same or similar problem to you check out my recent thread
http://discussions.apple.com/thread.jspa?threadID=245528&tstart=30
Powerbook, 512, 1GHz, 60 gig Mac OS X (10.3.6)

"Disk too slow or System Overload"

So while I'm doing rather simple things like recording vox or even playback, the audio stops and I get the message:
"Disk is too slow or System Overload.
(-10010)
The Sudden Motion Sensor may have parked the hard drive head, or the disk performance is not sufficient to read or write all audio tracks, or the system was not able to process all data in time."
I'm running on Intel Dual Core i5 2.3's, 4 gigs of RAM with about 230 gigs of free space. I have turned the SMS already to it can't be that. Does anyone know what the problem could be?

CosmicChild wrote:
Thanks for the reply. Mind if I ...probe... you for some more info?
Too many CPU intensive VI- what is VI?
HDDs- what is that?
thanks you!
VI = Virtual Instruments. Logic software instruments or third party software instruments.
HDD = Hard Disk Drive
pancenter-

Disk too slow and system overload error

I like many other users am having problems with the "disk too slow or system overload error (-10010)." It only seems to occur during playback attempts, seeing as I recorded with no problems yesterday, and only began happening today (granted, I have not tried recording anything since this started happening). I have tried changing the buffer size (still occurs at all levels), and, as per noted in a similar post, ensuring that my computer does not at any time put drives to sleep. All my sessions are stored on an external Toshiba Canvio Connect 2.0 TB drive connected directly to my computer via USB.
My setup (I know that this is going to draw a lot of criticism) is a macbook air with 2 gb 1067 MHz DDR3 ram and a 1.4 GHz intel core 2 duo processor, running OS X 10.9.3. While I am fully aware (I promise) that these are well below the recommended numbers, I have been using this configuration since June without any problems whatsoever.

Clancy,
No problem!
I also added it to the Useful links and resources for Logic Pro X page in the tips sections....
Cheers..
Nigel

Logic Pro X - Disk is too slow or System Overload. (-10010)

Hi there, I'm a professional music user and recently switched from Pro-Tools to Logic due to PT11's lack of third party plug-in support at the moment. I was looking forward to leaving behind the error messages of Pro-Tools for the supposed plain sailing of Logic. However, after installing Logic X and starting a new session with one track of audio and 4 tracks of software instruments, I'm receiving the following error message when attemping to record a part on one of the software instruments. 'Disk is too slow or System Overload. (-10010)'
I have an 8 core Mac Pro with the latest version of Mountain Lion, 16GB of Ram and a 250GB SSD boot drive (which Logic is installed on). My sessions are ran from a secondary 120GB SSD which has 110GB of free space on it and my sample libraries are streamed from another internal 250GB SSD and a 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive. My interface is a Focusrite Scarlett 6i6 USB 2.0 and my I/O buffer is set to 512.
It is completely unacceptable to me that I should be experiencing error messages with this set up and a 64 bit DAW, particularly when the session in question only has one track of audio and one instance of East West's Play engine, spread across 4 software instrument tracks.
Has anyone else experienced similar problems or have any ideas as to what the solution could be? I'd really appreciate any advice.
Cheers,
David

Just as a quick followup....
After doing a little research online it seems the Scarlett is one of those USB2 devices that has issues with how Apple changed their implementation of USB when they released Macs with USB3 interfaces and put this updated implementation into Lion and later Mountain Lion... and that this is probably why some people have major issues like the OP is reporting and why other's do not. It depends on the hardware/OS X version combination as to if this issue rears it's ugly head.
Oddly enough some Win 8 users are also reporting similar issues with the Scarlett for much the same reason.
The March 2013 Scarlett OS X drivers are intended to 'alleviate' this issue but Focusrite have stated it is only to 'alleviate' in some instances and not completely fix the problem for everyone who has it,.,..
However, the good news is that Focusrite have released some beta drivers (v1.7b2 and later b3) which seem to work better for some people than the last official release...
Mac Only.
General stability/logging improvements:
- Improved audio stream syncing
- Fixed bug which results in occasional inaccurate timestamps
- Improves sample rate switching
- 18i20 stream formats now switch automatically
- Fixes Forte streaming at 176.4/192kHz
You can find them here..
http://beta.focusrite.com
Note: These beta drivers again seem to only alleviate the issues for some people and not all but it has got to be worth giving them a try I would think...

Disk is too slow or System Overload Errors(-10010)

Hi, It may have been a mistake, but for the 1st time in a long time, I updated my system and software two days ago, after which i tried to runm Logic 9. During playback, I am not getting a random error message that "Disk is too slow or System orverload. This is a system that has operated error free for the past eighteen months, no problems, until now! What really puzzles me about this is the part about "motion Sensor" ! My system is a Mac Pro Desktop unit and not a laptop, and definitely not equipped with and motion sensor(s) at least not that I am aware of.
Can nyone shed some light on this for me?
Thanks in advance

Hi
rockfort wrote:
Did you repair permissions after the OS update?
** I don't know how**
To repair Permissions, in the Finder, use the Go:Utilities function, and run Disk Utility.
In Disk Utility, select the boot drive partition on the left and click on "Repair Disk Permissions".
rockfort wrote:
Free space on the OS and/or Project drive(s)?
** 1.78TB space free on the drive**
So, are you recording /playing back your projects from your System drive?
This is not generally recommended. Instead one should really use an second (Project) drive either Internal (no good for an iMac) or external Firewire/Thunderbolt drive (depends which iMac you have).
Further, the error message you have been getting is a general "Disk too slow" and/or "CPU overloaded" message.
It would be worth keeping an eye on the System Performance meter in Logic whilst playing the project (Double click on the CPU meter in the Transport or use :Options:Audio:System Performance) to see if it is CPU or Disk related
CCT

Disk is too slow or System Overload. (-10009)

Hello all,
I'm running a G4 PowerBook, with 1.67 GHz, and 1.5 GB DDR SDRAM. My Logic set-up is Logic Pro 7 and a Motu 828mkII.
My present Logic project contains 7 tracks, with EXS24 through 6 tracks and Sculpture through the last. The instruments were triggered through a midi keyboard.
While trying to score a short film, I keep running into the following error:
CoreAudio: Disk is too slow or System Overload. (-10009). The error happens while recording and during playback only. There are times when I do not recieve the error message, but playback is terribly jerky and I'm unable to clearly see exactly where I am on the timeline.
I have searched for similar errors on this site and cannot seem to find an answer. I imagine the solution is changing the way I have my I/O setting in the CPU usage. Am I on base?
I'd appreciate any help,
Kris

Hey Cyril and 25G's,
Well I went out and bought a OWC Mercury Elite Pro Firewire 800 with Oxford 912. I transferred the EXS Factory Sample files to the OWC drive. Then I deleted the EXS Factory Sample files on the OS hard disk. Then I created the alias for the Samples and placed the alias back in the Logic file under Application Support on the OS hard disk.
The alias' seem to be working because the Logic project works. The only problem is that it is still terribly jerky.
The CPU is maxing out while the I/O meter is not responding at all. Could this be the clue to my problem?
(Also, Cyril, call me stupid, but I cannot find the Virtual Memory portion in the EXS Preferences.)
Thank you for all your help. (I am a bit slow myself when it comes to Logic and the proper steps to de-bugging a problem. So, very detailed explanations are appreciated)

Unusualy slow openbox system.[Solved]

Similar Messages

Maybe you are looking for